| /linux-4.4.14/arch/alpha/lib/ |
| D | strncpy.S | 72 1: ldq_u $1, 0($16) # clear the leading bits in the final word
|
| D | ev67-strrchr.S | 102 subq t5, t2, t5 # E : Normalize leading zero count
|
| D | ev6-copy_user.S | 65 and $6,7,$3 # .. .. .. E : is leading dest misalignment
|
| D | stxcpy.S | 258 lda t2, -1 # e1 : mask out leading garbage in source
|
| D | ev6-stxcpy.S | 288 lda t2, -1 # E : mask out leading garbage in source
|
| D | stxncpy.S | 162 mskqh t1, a0, t1 # e0 : mask leading garbage in src
|
| D | ev6-stxncpy.S | 202 mskqh t1, a0, t1 # U : mask leading garbage in src (stall)
|
| /linux-4.4.14/Documentation/pcmcia/ |
| D | driver.txt | 15 All fields are passed in as hexadecimal values (no leading 0x).
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | omap-gpmc-smsc9221.dtsi | 5 * or smsc 9218) has faster timings, leading to higher
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | README | 12 the problems is with leading underscores on kernel symbols. Elf
13 kernels have no leading underscores, a.out compiled kernels do. I
|
| /linux-4.4.14/kernel/ |
| D | Kconfig.hz | 15 environment leading to NR_CPUS * HZ number of timer interrupts
|
| /linux-4.4.14/Documentation/i2c/ |
| D | ten-bit-addresses | 6 address space, namely 0xa000-0xa3ff. The leading 0xa (= 10) represents the
|
| /linux-4.4.14/Documentation/fmc/ |
| D | parameters.txt | 42 golden gateware for the SPEC card, removing the leading timestamps to
|
| D | carrier.txt | 39 uint8_t *eeprom; /* Full contents or leading part */
|
| /linux-4.4.14/drivers/target/iscsi/ |
| D | iscsi_target_parameters.c | 572 int leading) in iscsi_copy_param_list() argument
587 if (!leading && (param->scope & SCOPE_SESSION_WIDE)) { in iscsi_copy_param_list()
1616 int leading) in iscsi_set_session_parameters() argument
1629 if (leading) in iscsi_set_session_parameters()
1646 if (leading) in iscsi_set_session_parameters()
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | decbin.S | 36 | A3. Count the number of leading/trailing zeros in the
37 | bcd string. If SE is positive, count the leading zeros;
|
| /linux-4.4.14/arch/c6x/lib/ |
| D | divremu.S | 23 ;; out how many leading zero bits there are in the divisor. This
|
| D | divu.S | 40 ;; out how many leading zero bits there are in the divisor. This
|
| /linux-4.4.14/arch/sh/ |
| D | Kconfig.debug | 55 This prints out a code trace of the instructions leading up to
|
| /linux-4.4.14/Documentation/s390/ |
| D | DASD | 12 parameters are to be given in hexadecimal notation without a leading
|
| /linux-4.4.14/Documentation/ |
| D | rtc.txt | 157 the epoch by default, or if there's a leading +, seconds in the
158 future, or if there is a leading +=, seconds ahead of the current
|
| D | printk-formats.txt | 166 leading zeros.
|
| D | sysfs-rules.txt | 49 - the kernel's path to the device directory without the leading
|
| D | stable_api_nonsense.txt | 127 the older, broken one would have had to be maintained over time, leading
|
| D | robust-futexes.txt | 47 is needed to release that futex based lock. This is one of the leading
|
| D | rbtree.txt | 214 leading to the inserted node, then call rb_link_node() as usual and
|
| D | ManagementStyle | 272 for being "in charge". Never mind the fact that you're really leading
|
| D | workqueue.txt | 50 those very limited execution contexts leading to various problems
|
| D | atomic_ops.txt | 41 As with all of the atomic_ interfaces, replace the leading "atomic_"
|
| D | memory-barriers.txt | 534 leading to the following situation:
2836 instruction before moving on to the next one, leading to a definite sequence of
2852 (*) loads may be done speculatively, leading to the result having been fetched
|
| D | kernel-parameters.txt | 1989 will cause delays in the kernel to be wrong, leading to
4136 consumption unbound, leading to measurably lower
|
| D | devices.txt | 3266 number without leading zeroes.
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.cpia2 | 110 overwrite the third buffer before the read finishes, leading to a corrupt
|
| D | v4l2-framework.txt | 1067 This way no status information is lost, just the intermediate steps leading
|
| /linux-4.4.14/tools/perf/config/ |
| D | utilities.mak | 166 # by the presence of a leading `/'.
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Insmod-options | 53 quality which leading to unwanted sound
|
| /linux-4.4.14/Documentation/usb/ |
| D | proc_usb_info.txt | 110 d = decimal number (may have leading spaces or 0's)
111 x = hexadecimal number (may have leading spaces or 0's)
|
| D | CREDITS | 79 leading manufacturer for active and passive ISDN Controllers
|
| D | usbmon.txt | 130 have leading zeros, for the sake of human readers.
|
| /linux-4.4.14/Documentation/early-userspace/ |
| D | README | 81 Where's this all leading?
|
| /linux-4.4.14/scripts/ |
| D | checkpatch.pl | 1898 my ($leading) = @_;
1905 1 while $leading =~ s@^([\t]*)$spaces_to_tab@$1\t@g;
1907 1 while $leading =~ s@^([\t]*)( {1,$max_spaces_before_tab})\t@$1\t@g;
1909 return "$leading";
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-summary | 100 clock starts low, so the first (leading) edge is rising, and
102 starts high, so the first (leading) edge is falling.
105 sample on the leading edge, CPHA=1 means the trailing edge.
|
| /linux-4.4.14/Documentation/accounting/ |
| D | taskstats.txt | 163 up with the kernel's rate of sending per-tid/tgid exit data leading to data
|
| /linux-4.4.14/Documentation/networking/ |
| D | PLIP.txt | 120 nibbles into bytes, leading to much faster transfers.
|
| D | arcnet-hardware.txt | 57 completely different programming interface, leading to a lot of different,
|
| /linux-4.4.14/arch/arm/nwfpe/ |
| D | softfloat-macros | 637 Returns the number of leading 0 bits before the most-significant 1 bit
679 Returns the number of leading 0 bits before the most-significant 1 bit
|
| /linux-4.4.14/Documentation/timers/ |
| D | hrtimers.txt | 24 the wheel concept, leading to even worse compromises. The timer wheel
|
| D | timekeeping.txt | 42 potentially being updated in between leading to the risk of very strange
|
| /linux-4.4.14/Documentation/scsi/ |
| D | FlashPoint.txt | 42 Mylex Corporation (NASDAQ/NM SYMBOL: MYLX), founded in 1983, is a leading
|
| D | ChangeLog.1992-1997 | 1964 * scsi.c: Ignore leading spaces when looking for blacklisted devices.
|
| D | ChangeLog.lpfc | 1244 * Formatting changes: get rid of leading spaces in code
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | overlayfs.txt | 199 relative paths leading up to the filesystem's root. This will be
|
| D | porting | 225 a few holes of that kind - unprotected access to ->d_parent leading to
|
| D | ext2.txt | 257 which would leading to inconsistent bitmaps. An old kernel would also
|
| /linux-4.4.14/drivers/media/usb/pwc/ |
| D | philips.txt | 174 leading zeroes (it's treated as a string).
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 186 leading to surprises when you run programs on different machines that
|
| /linux-4.4.14/drivers/net/ethernet/broadcom/bnx2x/ |
| D | bnx2x_cmn.h | 129 bool leading);
|
| D | bnx2x_main.c | 3122 bool leading) in bnx2x_get_q_flags() argument
3143 if (leading) { in bnx2x_get_q_flags()
8742 int tx_index, bool leading) in bnx2x_setup_tx_only() argument
8783 bool leading) in bnx2x_setup_queue() argument
8823 setup_params->flags = bnx2x_get_q_flags(bp, fp, leading); in bnx2x_setup_queue()
8855 tx_only_params, tx_index, leading); in bnx2x_setup_queue()
|
| /linux-4.4.14/kernel/power/ |
| D | Kconfig | 296 significantly to power consumption unbound, leading to measurably
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 7.AdvancedTopics | 98 advances, it is tempting to merge with that tree to stay on the leading
|
| D | 2.Process | 27 thus the leading edge of Linux kernel development; the kernel uses a
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | pmbus-core | 15 time to market for power system designers. Pioneered by leading power supply and
|
| /linux-4.4.14/Documentation/locking/ |
| D | lockdep-design.txt | 130 Exception: Nested data dependencies leading to nested locking
|
| /linux-4.4.14/arch/arm/mm/ |
| D | Kconfig | 703 with SWP emulation enabled, leading to deadlock of the user
960 writes to be retained when the memory system is idle, leading
|
| /linux-4.4.14/Documentation/power/ |
| D | freezing-of-tasks.txt | 218 leading to freezing failure.
|
| D | swsusp.txt | 219 Q: After resuming, system is paging heavily, leading to very bad interactivity.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | stallwarn.txt | 249 leading the realization that the CPU had failed.
|
| D | trace.txt | 394 o The leading number is the CPU number, with "!" indicating
|
| /linux-4.4.14/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 320 This is a transient state, leading immediately to
|
| /linux-4.4.14/Documentation/fb/ |
| D | matroxfb.txt | 71 You can enter these number either hexadecimal (leading `0x') or decimal
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kconfig-language.txt | 520 Confirming this could prove useful as Kconfig stands as one of the the leading
|
| /linux-4.4.14/arch/arm64/ |
| D | Kconfig | 617 with SWP emulation enabled, leading to deadlock of the user
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README | 429 Euro-ISDN does not transmit the leading '0' of the caller-id for an
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci.txt | 161 All fields are passed in as hexadecimal values (no leading 0x).
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 1167 potentially leading to corrupted entries in the cache or TLB.
1686 precious low memory, eventually leading to low memory being
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 923 the trace leading up to that latency point so that every time a
2846 usually leading to a system panic.
|
| /linux-4.4.14/drivers/scsi/ |
| D | Kconfig | 243 busses in parallel, leading to a significant speed-up.
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | booting-without-of.txt | 896 (unit addresses do not require leading zeroes)
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | fpsp.S | 8960 # where L1, L2 are the leading and trailing parts of #
|