| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-class-net-statistics | 23 See the network driver for the exact meaning of when this
51 packet processing. See the network driver for the exact
60 network device. See the network driver for the exact
71 the exact meaning of this value.
80 exact meaning of this value.
89 driver for the exact meaning of this value.
98 (e.g: larger than MTU). See the network driver for the exact
116 a medium collision). See the network driver for the exact
125 device. See the network driver for the exact meaning of this
137 network driver for the exact meaning of this value.
[all …]
|
| D | sysfs-firmware-ofw | 27 in the directory. The contents of each file is the exact
|
| D | sysfs-driver-hid-logitech-lg4ff | 19 wheel into the corresponding mode. Depending on the exact model
|
| D | sysfs-bus-iio | 558 depending on the exact set requested. So if you want to be
612 vary depending on the exact set requested. So if you want to be
|
| /linux-4.1.27/arch/metag/tbx/ |
| D | tbistring.c | 29 bool exact = true; in __TBIFindStr() local
35 exact = false; in __TBIFindStr()
71 (!exact || (search->Len == match_len + 1)) && in __TBIFindStr()
|
| /linux-4.1.27/crypto/ |
| D | crypto_user.c | 47 static struct crypto_alg *crypto_alg_match(struct crypto_user_alg *p, int exact) in crypto_alg_match() argument
62 else if (!exact) in crypto_alg_match()
396 int exact = 0; in crypto_add_alg() local
409 exact = 1; in crypto_add_alg()
411 if (priority && !exact) in crypto_add_alg()
414 alg = crypto_alg_match(p, exact); in crypto_add_alg()
|
| D | api.c | 66 int exact, fuzzy; in __crypto_alg_lookup() local
79 exact = !strcmp(q->cra_driver_name, name); in __crypto_alg_lookup()
81 if (!exact && !(fuzzy && q->cra_priority > best)) in __crypto_alg_lookup()
92 if (exact) in __crypto_alg_lookup()
|
| /linux-4.1.27/drivers/net/ethernet/chelsio/cxgb4vf/ |
| D | t4vf_hw.c | 1202 unsigned int fw_naddr = (rem < ARRAY_SIZE(cmd.u.exact) in t4vf_alloc_mac_filt()
1204 : ARRAY_SIZE(cmd.u.exact)); in t4vf_alloc_mac_filt()
1206 u.exact[fw_naddr]), 16); in t4vf_alloc_mac_filt()
1220 for (i = 0, p = cmd.u.exact; i < fw_naddr; i++, p++) { in t4vf_alloc_mac_filt()
1233 for (i = 0, p = rpl.u.exact; i < fw_naddr; i++, p++) { in t4vf_alloc_mac_filt()
1285 struct fw_vi_mac_exact *p = &cmd.u.exact[0]; in t4vf_change_mac()
1287 u.exact[1]), 16); in t4vf_change_mac()
1311 p = &rpl.u.exact[0]; in t4vf_change_mac()
1334 u.exact[0]), 16); in t4vf_set_addr_hash()
|
| /linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/ |
| D | cdns,xtensa-mx.txt | 6 Remaining properties have exact same meaning as in Xtensa PIC
|
| /linux-4.1.27/arch/sh/drivers/ |
| D | Kconfig | 9 Use the power-on LED on your machine as a load meter. The exact
|
| /linux-4.1.27/scripts/genksyms/ |
| D | genksyms.h | 64 struct symbol *find_symbol(const char *name, enum symbol_type ns, int exact);
|
| D | genksyms.c | 166 struct symbol *find_symbol(const char *name, enum symbol_type ns, int exact) in find_symbol() argument
177 if (exact && sym && sym->type != ns) in find_symbol()
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/ |
| D | pwm-clock.txt | 17 is not exact but was rounded to nanoseconds.
|
| /linux-4.1.27/fs/gfs2/ |
| D | rgrp.h | 31 extern struct gfs2_rgrpd *gfs2_blk2rgrpd(struct gfs2_sbd *sdp, u64 blk, bool exact);
|
| D | rgrp.c | 503 struct gfs2_rgrpd *gfs2_blk2rgrpd(struct gfs2_sbd *sdp, u64 blk, bool exact) in gfs2_blk2rgrpd() argument
519 if (exact) { in gfs2_blk2rgrpd()
|
| /linux-4.1.27/Documentation/networking/ |
| D | gianfar.txt | 28 filtering. On the eTSEC, the exact-match MAC registers are used
|
| D | openvswitch.txt | 79 The <linux/openvswitch.h> header file defines the exact format of the
101 A wildcarded flow can represent a group of exact match flows. Each '1' bit
102 in the mask specifies a exact match with the corresponding bit in the flow key.
108 space program. The kernel can ignore the mask attribute, installing an exact
|
| D | can.txt | 228 and have to be logged together with the exact timestamp. For this
|
| D | bonding.txt | 506 setting this option to 0 or to 1 has the exact same effect.
|
| /linux-4.1.27/Documentation/devicetree/bindings/dma/ |
| D | jz4780-dma.txt | 44 the client. Otherwise, the exact channel specified will be used. The channel
|
| /linux-4.1.27/fs/ubifs/ |
| D | tnc.c | 1162 int err, exact; in ubifs_lookup_level0() local
1181 exact = ubifs_search_zbranch(c, znode, key, n); in ubifs_lookup_level0()
1203 if (exact || !is_hash_key(c, key) || *n != -1) { in ubifs_lookup_level0()
1204 dbg_tnc("found %d, lvl %d, n %d", exact, znode->level, *n); in ubifs_lookup_level0()
1205 return exact; in ubifs_lookup_level0()
1298 int err, exact; in lookup_level0_dirty() local
1320 exact = ubifs_search_zbranch(c, znode, key, n); in lookup_level0_dirty()
1347 if (exact || !is_hash_key(c, key) || *n != -1) { in lookup_level0_dirty()
1348 dbg_tnc("found %d, lvl %d, n %d", exact, znode->level, *n); in lookup_level0_dirty()
1349 return exact; in lookup_level0_dirty()
|
| /linux-4.1.27/Documentation/misc-devices/ |
| D | ad525x_dpot.txt | 23 and may vary greatly on a part-by-part basis. For exact interpretation of
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | lm95245 | 39 It will round up to the next selectable interval. See the datasheet for exact
|
| D | lm95234 | 39 It will round up to the next selectable interval. See the datasheet for exact
|
| D | adt7462 | 19 two. See the chip documentation for more details about the exact set of
|
| D | lm75 | 87 they reproduce the exact register tricks of the original LM75, and must
|
| D | w83781d | 279 You can handle all 3 the exact same way :)
420 remember the exact value) would be 70% and higher would be full on.
|
| D | sysfs-interface | 59 between readings to be caught and alarmed. The exact definition of an
|
| /linux-4.1.27/Documentation/devicetree/bindings/pwm/ |
| D | pwm.txt | 16 PWM properties should be named "pwms". The exact meaning of each pwms
|
| /linux-4.1.27/Documentation/netlabel/ |
| D | introduction.txt | 31 protocol built on top of the Generic NETLINK transport mechanism. The exact
|
| D | lsm_interface.txt | 37 Depending on the exact configuration, translation between the network packet
|
| /linux-4.1.27/Documentation/devicetree/bindings/i2c/ |
| D | i2c-pxa-pci-ce4100.txt | 12 of the specific I2C controller. This were his exact words:
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | isofs.txt | 21 check=strict Matches only filenames with the exact same case
|
| D | squashfs.txt | 46 compressed inode is on average 8 bytes in length (the exact length varies on
|
| D | fuse.txt | 255 exact sequence and timing of operations performed. This
|
| D | sharedsubtree.txt | 481 exact same configuration as that of 'B'. This new propagation tree
498 in the exact same configuration as that of 'B'. This new propagation
|
| D | path-lookup.txt | 64 exact path walking flags.
|
| /linux-4.1.27/arch/m68k/ |
| D | Kconfig | 108 initially work for you. As of this writing the exact hardware
|
| D | Kconfig.devices | 14 Use the power-on LED on your machine as a load meter. The exact
|
| D | Kconfig.cpu | 439 specific to the exact CPU that you are using.
|
| /linux-4.1.27/Documentation/kbuild/ |
| D | kconfig.txt | 171 - first, exact matches, sorted alphabetically (an exact match
|
| D | makefiles.txt | 550 cc-fullversion is useful when the exact version of gcc is needed.
|
| /linux-4.1.27/Documentation/power/ |
| D | opp.txt | 77 exact mechanism to trigger these or the notification mechanism to other
90 using RCU read locks. The opp_find_freq_{exact,ceil,floor},
140 dev_pm_opp_find_freq_exact - Search for an OPP based on an *exact* frequency and
|
| D | pci.txt | 376 state from which it can signal wakeup. The exact method of signaling wakeup is
|
| /linux-4.1.27/Documentation/pti/ |
| D | pti_intel_mid.txt | 68 // doubt you'll want to use these exact error lines of code
|
| /linux-4.1.27/drivers/net/wan/lmc/ |
| D | lmc_var.h | 159 u32 exact; member
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | machinecheck | 9 a hardware subsystem) and subevents in a bank. The exact meaning
|
| /linux-4.1.27/Documentation/RCU/ |
| D | rcu_dereference.txt | 25 for an example where the compiler can in fact deduce the exact
65 allow the compiler to deduce the exact value, which again can
364 the exact value of "p" even in the not-equals case. This allows the
|
| /linux-4.1.27/Documentation/video4linux/cx2341x/ |
| D | fw-dma.txt | 53 Results[2]: Size: The exact number of bytes to transfer.
|
| /linux-4.1.27/Documentation/bus-devices/ |
| D | ti-gpmc.txt | 47 most of the datasheets & hardware (to be exact none of those supported
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 27 The exact purpose of each gpios property must be documented in the device tree
77 value at the device. The exact definition of logically asserted should be
|
| /linux-4.1.27/arch/blackfin/ |
| D | Kconfig.debug | 39 bool "Try to make Hardware errors exact"
42 By default, the Blackfin hardware errors are not exact - the error
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | boost.txt | 67 not necessarily mean that it will occur every time even using the exact
|
| /linux-4.1.27/arch/powerpc/boot/dts/ |
| D | prpmc2800.dts | 11 * if it can determine the exact PrPMC type.
|
| /linux-4.1.27/Documentation/ |
| D | serial-console.txt | 77 like this to /etc/inittab (exact syntax depends on your getty):
|
| D | stable_api_nonsense.txt | 72 module for the exact specific kernel configuration, using the same exact
|
| D | rbtree.txt | 252 lo:hi or to find whether there is an exact match for a new lo:hi.
255 way making it possible to do efficient lookup and exact match.
|
| D | gcov.txt | 158 exact same file system location on the test machine as on the build
|
| D | BUG-HUNTING | 194 In addition, you can use GDB to figure out the exact file and line
|
| D | remoteproc.txt | 172 the exact virtqueue index to look in is optional: it is easy (and not
|
| D | nommu-mmap.txt | 198 The mremap() function must be given an exact match for base address and size of
|
| D | svga.txt | 37 for exact meaning of the ID). Warning: rdev and LILO don't support
|
| D | atomic_ops.txt | 539 The routines xchg() and cmpxchg() must provide the same exact
|
| D | pinctrl.txt | 870 Depending on the exact HW register design, some functions exposed by the
1351 This gives the exact same result as the above construction.
|
| D | HOWTO | 509 the exact opposite of what companies are used to doing. Your proposal
|
| D | kprobes.txt | 578 exact instance of the kretprobe that caused the problem. We have the
|
| D | DMA-API-HOWTO.txt | 482 You should provide the exact DMA direction if you know it.
|
| D | kernel-parameters.txt | 1241 highmem=nn[KMG] [KNL,BOOT] forces the highmem zone to have an exact
1980 memmap=exactmap [KNL,X86] Enable setting of an exact
3909 vmalloc=nn[KMG] [KNL,BOOT] Forces the vmalloc area to have an exact
|
| /linux-4.1.27/Documentation/gpio/ |
| D | board.txt | 20 exact way to do it depends on the GPIO controller providing the GPIOs, see the
|
| D | gpio.txt | 41 The exact capabilities of GPIOs vary between systems. Common options:
|
| D | gpio-legacy.txt | 28 The exact capabilities of GPIOs vary between systems. Common options:
480 exact name string of pinctrl device has to be passed as one of the
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-parport | 73 - This is the exact pinout and electronics used on the Analog Devices
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-domains.txt | 46 to our runqueue. The exact number of tasks amounts to an imbalance previously
|
| /linux-4.1.27/arch/m68k/fpsp040/ |
| D | setox.S | 108 | b) N*L1 is exact because N is no longer than 22 bits and
110 | c) The calculation X+N*L1 is also exact due to cancellation.
149 | will all be exact --- a property that will give much
|
| D | stan.S | 334 faddx FP_SCR2(%a6),%fp0 |high part of reduction is exact
|
| D | do_func.S | 324 bra t_resdnrm |force UNFL(but exact) result
|
| D | bindec.S | 612 | be inexact, since all powers of ten up to 10^27 are exact
|
| D | res_func.S | 1561 fbeq int_wrt |exact answer
1569 fbeq int_wrt |exact answer
|
| D | round.S | 46 | If g=r=s=0 then result is exact and round is done, else set
|
| /linux-4.1.27/arch/arm/nwfpe/ |
| D | softfloat-macros | 554 divisor `b' must be at least 2^63. If q is the exact quotient truncated
556 If the exact quotient q is larger than 64 bits, the maximum positive 64-bit
599 case, the approximation returned lies strictly within +/-2 of the exact
|
| /linux-4.1.27/arch/x86/math-emu/ |
| D | README | 116 (c) the magnitude of the exact result (before rounding) is less than 2^-16382.
118 (e) the magnitude of the exact result would be exactly 2^-16382 if the
234 return exact results; they have no error.
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | usage-model.txt | 117 with the exact name of the machine, followed by an optional list of
125 Where "ti,omap3-beagleboard-xm" specifies the exact model, it also
128 specific (exact board) to least specific (SoC family).
|
| D | booting-without-of.txt | 849 kernel, you would specify the exact board model in the
|
| /linux-4.1.27/arch/m68k/q40/ |
| D | README | 132 - exact keypress/release sequence
|
| /linux-4.1.27/Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 64 IOMMU binding for the exact meaning of the cells that make up the specifier.
|
| /linux-4.1.27/drivers/net/wireless/rt2x00/ |
| D | Kconfig | 194 have a rt28xx family compatible chipset, but for which the exact
|
| /linux-4.1.27/net/core/ |
| D | pktgen.c | 448 const char *ifname, bool exact);
1901 bool exact = (remove == FIND); in __pktgen_NN_threads() local
1904 pkt_dev = pktgen_find_dev(t, ifname, exact); in __pktgen_NN_threads()
3505 const char *ifname, bool exact) in pktgen_find_dev() argument
3514 if (exact || p->odevname[len] != '@') in pktgen_find_dev()
|
| /linux-4.1.27/Documentation/input/ |
| D | ff.txt | 82 Note: The exact syntax FF_CUSTOM is undefined for the time being as no driver
|
| D | joystick-parport.txt | 458 The exact type of the PSX controller type is autoprobed when used, so
|
| /linux-4.1.27/arch/arm/mach-ixp4xx/ |
| D | Kconfig | 91 # IXCDP1100 is the exact same HW as IXDP425, but with a different machine
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 44 At the time of writing, exact chip may be either 'fsl,mpc5200' or
|
| /linux-4.1.27/Documentation/devicetree/bindings/ |
| D | xilinx.txt | 48 Typically, the compatible list will include the exact IP core version
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | CMIPCI.txt | 244 If the auto-detection fails, try to pass the exact I/O address.
|
| D | ALSA-Configuration.txt | 898 users from specifying exact period/buffer sizes.
|
| /linux-4.1.27/Documentation/hid/ |
| D | uhid.txt | 176 kernel with the exact same "id" as in the request. If the request already
|
| /linux-4.1.27/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 123 exact number that a driver asks for.
279 exact number that a driver asks for.
|
| /linux-4.1.27/Documentation/m68k/ |
| D | kernel-options.txt | 15 kernel understands, or how the exact syntax for the ... option is, or
179 memory faults or bad kernel traps, and kernel panics. To be exact: all
203 lock up). The timeout is not exact, but usually a few
|
| /linux-4.1.27/arch/sh/lib/ |
| D | memcpy-sh4.S | 194 ! Deciding on an exact value of 'small' is not easy, as the point at which
|
| /linux-4.1.27/Documentation/isdn/ |
| D | INTERFACE | 98 The struct isdn_ctrl also defined in isdn_if. The exact meanings of its
114 setup, etc. The exact meaning of the parameters is described with the
|
| D | INTERFACE.CAPI | 216 represent. See <linux/isdn/capiutil.h> for the exact spelling. Member data
|
| /linux-4.1.27/drivers/net/ethernet/sun/ |
| D | niu.h | 2737 exact:1, member
2743 exact:1, member
|
| /linux-4.1.27/Documentation/locking/ |
| D | ww-mutex-design.txt | 79 * Functions to only acquire a single w/w mutex, which results in the exact same
|
| /linux-4.1.27/arch/sparc/ |
| D | Kconfig | 271 Loading this driver allows exact mnemonic strings to be
|
| /linux-4.1.27/Documentation/trace/ |
| D | ftrace-design.txt | 33 The exact mcount symbol name will depend on your toolchain. Some call it
|
| /linux-4.1.27/arch/ia64/ |
| D | Kconfig | 554 initially work for you. As of this writing the exact hardware
|
| /linux-4.1.27/Documentation/i2c/ |
| D | writing-clients | 175 don't know the exact address it uses. This happens on TV adapters for
|
| /linux-4.1.27/drivers/net/ethernet/chelsio/cxgb4/ |
| D | t4_hw.c | 4626 for (i = 0, p = c.u.exact; i < naddr; i++, p++) { in t4_alloc_mac_filt()
4636 for (i = 0, p = c.u.exact; i < naddr; i++, p++) { in t4_alloc_mac_filt()
4673 struct fw_vi_mac_exact *p = c.u.exact; in t4_change_mac()
|
| D | t4fw_api.h | 1935 } exact[7]; member
|
| /linux-4.1.27/Documentation/security/ |
| D | Smack.txt | 219 1 - exact: this is the policy that limits PTRACE_ATTACH. Attach is
222 2 - draconian: this policy behaves like the 'exact' above with an
|
| D | keys.txt | 1241 to the default matcher function (which does an exact description match
|
| /linux-4.1.27/arch/sh/ |
| D | Kconfig | 615 initially work for you. As of this writing the exact hardware
|
| /linux-4.1.27/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 256 which exact CPUs within the cluster play these roles. This must
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 283 of the VF(n) BAR space in the VF BAR. If the PCI core allocates the exact
|
| D | hvcs.txt | 233 env variable is set to the exact terminal type of the terminal emulator
|
| /linux-4.1.27/drivers/md/ |
| D | Kconfig | 85 A RAID-1 set consists of several disk drives which are exact copies
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | memory.txt | 563 method and doesn't show 'exact' value of memory (and swap) usage, it's a fuzz
565 If you want to know more exact memory usage, you should use RSS+CACHE(+SWAP)
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.megaraid | 528 now released in the exact reverse order of the allocation time
|
| D | ChangeLog.megaraid_sas | 460 It does, but the DMA API was expanded to cope with this exact case, so
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | v4l2-controls.txt | 203 as the last argument an array of signed 64-bit integers that form an exact
|
| D | vivid.txt | 379 Like with video capture the framerate is also exact in the long term.
|
| D | v4l2-framework.txt | 563 know the exact i2c address so in that case no probing will take place.
|
| /linux-4.1.27/arch/powerpc/ |
| D | Kconfig | 426 initially work for you. As of this writing the exact hardware
|
| /linux-4.1.27/net/bluetooth/ |
| D | l2cap_core.c | 7192 int exact = 0, lm1 = 0, lm2 = 0; in l2cap_connect_ind() local
7207 exact++; in l2cap_connect_ind()
7216 return exact ? lm1 : lm2; in l2cap_connect_ind()
|
| /linux-4.1.27/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 1354 # branch to _real_inex() (even if the result was exact!);
1932 # branch to _real_inex() (even if the result was exact!);
|
| D | fpsp.S | 1355 # branch to _real_inex() (even if the result was exact!);
1933 # branch to _real_inex() (even if the result was exact!);
4185 # no exception that was enabled was set BUT if we got an exact overflow
5599 fadd.x FP_SCR0(%a6),%fp0 # high part of reduction is exact
7041 # T-2, and T-8 will all be exact --- a property that will #
|
| D | fplsp.S | 5924 fadd.x FP_SCR0(%a6),%fp0 # high part of reduction is exact
6764 # b) N*L1 is exact because N is no longer than 22 bits #
6766 # c) The calculation X+N*L1 is also exact due to #
6807 # T-2, and T-8 will all be exact --- a property that will #
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 377 exact clock and bus design, the drift may or may not be fixed in absolute
|
| /linux-4.1.27/init/ |
| D | Kconfig | 629 This option forces use of the exact RCU_FANOUT value specified,
876 used as it forces an exact (power of two) size of the ring buffer.
|
| /linux-4.1.27/Documentation/usb/ |
| D | power-management.txt | 84 exact definition depends on the device's driver; drivers are allowed
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 531 the exact frame boundaries, since there are no synchronization headers
|
| /linux-4.1.27/arch/mips/ |
| D | Kconfig | 2600 initially work for you. As of this writing the exact hardware
|
| /linux-4.1.27/drivers/scsi/ |
| D | Kconfig | 953 forces a small delay (1.0 usec to be exact) after changing the
|
| /linux-4.1.27/arch/x86/ |
| D | Kconfig | 1730 initially work for you. As of this writing the exact hardware
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 3883 The exact boot error depends on the distribution that you're booting,
|