| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | qcom,spmi-regulator.txt | 126 BIT(0) = follow HW0_EN signal
127 BIT(1) = follow HW1_EN signal
128 BIT(2) = follow HW2_EN signal
129 BIT(3) = follow HW3_EN signal
138 BIT(0) = follow HW0_EN signal
139 BIT(1) = follow HW1_EN signal
140 BIT(2) = follow HW2_EN signal
141 BIT(3) = follow HW3_EN signal
142 BIT(4) = follow PMIC awake state
|
| D | max77686.txt | 22 to get matched with their hardware counterparts as follow:
|
| D | max77802.txt | 42 with their hardware counterparts as follow. The valid names are:
|
| /linux-4.4.14/fs/coda/ |
| D | pioctl.c | 67 if (data.follow) in coda_pioctl()
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/rockchip/ |
| D | smp-sram.txt | 14 The rest of the properties should follow the generic mmio-sram discription
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | arasan,sdhci.txt | 3 The bindings follow the mmc[1], clock[2] and interrupt[3] bindings. Only
|
| D | mmc-spi-slot.txt | 14 Write-Protect GPIO. Note that this does not follow the
|
| D | mmc.txt | 54 line levels. We choose to follow the SDHCI standard, which specifies both those
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/exynos/ |
| D | smp-sysram.txt | 17 The rest of the properties should follow the generic mmio-sram discription
|
| /linux-4.4.14/drivers/staging/media/ |
| D | Kconfig | 7 Most of them don't follow properly the V4L, DVB and/or RC API's,
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-firmware-ofw | 15 path directly, but instead should follow /proc/device-tree
|
| D | sysfs-platform-eeepc-laptop | 39 is defined as follow:
|
| D | sysfs-platform-asus-laptop | 7 is composed by 4 bits and defined as follow:
|
| D | sysfs-bus-pci | 134 device. It should follow the VPD format defined in
|
| /linux-4.4.14/Documentation/ |
| D | stable_kernel_rules.txt | 26 - It must follow the Documentation/SubmittingPatches rules.
32 - If the patch covers files in net/ or drivers/net please follow netdev stable
36 process but should follow the procedures in Documentation/SecurityBugs.
|
| D | lzo.txt | 29 Optionally depending on the opcode and operands, extra data may follow. These
72 follow because it has already been garanteed before parsing the instructions.
80 0..17 : follow regular instruction encoding, see below. It is worth
|
| D | IRQ-affinity.txt | 65 to follow the pertinent one.
|
| D | cputopology.txt | 103 [see <linux/cpumask.h>]. Some examples follow.
|
| D | sysfs-rules.txt | 11 of sysfs must follow some rules to use an as-abstract-as-possible way to
16 But if you really do want or need to access sysfs directly, please follow
|
| D | CodingStyle | 375 exported, the EXPORT* macro for it should follow immediately after the closing
405 - unconditional statements are easier to understand and follow
785 for us... but it doesn't. To help prevent such bugs, always follow this
885 files; doing so makes code harder to read and logic harder to follow. Instead,
890 remain easy to follow.
|
| D | local_ops.txt | 53 * Rules to follow when using local atomic operations
|
| D | SubmittingDrivers | 42 The same rules apply as 2.4 except that you should follow linux-kernel
|
| D | magic-number.txt | 22 Please follow this discipline when you are adding future enhancements
|
| D | kref.txt | 32 Once you have an initialized kref, you must follow the following
|
| D | HOWTO | 97 rationale behind it. All new code is expected to follow the
132 please follow the steps in this document to help notify the kernel
391 Please remember to follow good behavioral habits when using the lists.
|
| D | assoc_array.txt | 543 new layout until we follow the back pointers - at which point we've
551 This won't affect us until we follow the back pointers. Similar to (4).
|
| D | rbtree.txt | 79 root, compare each value, and follow the left or right branch as necessary.
|
| D | remoteproc.txt | 240 * its @type. The content of the entry itself will immediately follow
|
| D | oops-tracing.txt | 92 The hex bytes that follow "Code:" may (in some architectures) have a series
|
| D | kernel-docs.txt | 32 The papers that follow are listed in no particular order. All are
466 packets follow from the time they are received at the network
|
| D | xillybus.txt | 250 doesn't follow the common practice of checking a status register when it's
|
| D | atomic_ops.txt | 550 The rule to follow is simple:
|
| D | applying-patches.txt | 63 If you just want to be able to follow the examples below and don't want to
|
| D | adding-syscalls.txt | 57 together with the corresponding follow-up system calls -- eventfd/eventfd2,
|
| D | edac.txt | 54 There are several add-in adapters that do *not* follow the PCI specification
|
| D | kmemcheck.txt | 334 Now we need to follow the "pending" pointer, since that is being passed on to
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | review-checklist.txt | 4 1. The patch must follow Documentation/CodingStyle and
|
| D | nested-vmx.txt | 42 the lab, and will be sent as follow-on patchsets.
|
| D | api.txt | 2275 as follow:
2456 many valid HPT entries there are and how many invalid entries follow
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | packet-writing.txt | 51 However, some drives don't follow the specification and expect the
53 follow the specification, but suffer bad performance problems if the
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | gfs2-uevents.txt | 15 is successful, an ONLINE uevent will follow. If it is not successful
16 then a REMOVE uevent will follow.
|
| D | automount-support.txt | 40 To do expiration, you need to follow these steps:
|
| D | afs.txt | 113 presents these to the user as directories that have a follow-link capability
|
| D | ramfs-rootfs-initramfs.txt | 206 archive if you follow it. It says "A typical way to generate the list
|
| D | spufs.txt | 33 The files in spufs mostly follow the standard behavior for regular sys-
|
| D | sharedsubtree.txt | 475 Details follow:
|
| D | vfs.txt | 437 follow_link: called by the VFS to follow a symbolic link to the
|
| D | coda.txt | 528 int follow;
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | index.txt | 39 http://vger.kernel.org/vger-lists.html#linux-pm and follow the
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | lm77 | 28 * When setting a limit, its hysteresis will automatically follow, the
|
| D | emc1403 | 49 * When setting a limit, its hysteresis will automatically follow, the
|
| D | lm83 | 32 list and an unconfirmed list follow. If you can confirm or infirm the
|
| D | w83793 | 89 trip points, defining a PWM/temperature curve which the chip will follow.
|
| D | submitting-patches | 12 * It should be unnecessary to mention, but please read and follow
|
| D | f71882fg | 128 fan should run at at this temp and which temp a fan should follow using the
|
| D | f71805f | 65 The wirings and resistor values suggested by Fintek are as follow:
|
| D | asc7621 | 122 Except where noted below, the sysfs entries created by this driver follow
|
| D | sysfs-interface | 28 drivers follow, so that an application program can scan for entries and
34 find all sensor chips, it is easier to follow the device symlinks from
|
| D | w83781d | 190 We chose to follow 782d.
|
| /linux-4.4.14/drivers/staging/media/davinci_vpfe/ |
| D | TODO | 28 files are present in staging itself, to build for dm365 follow below steps,
|
| /linux-4.4.14/tools/build/Documentation/ |
| D | Build.txt | 66 To follow the above example, the user provides following 'Build' files:
155 All existing '.cmd' files are included in the Build process to follow properly
|
| /linux-4.4.14/ |
| D | REPORTING-BUGS | 138 Linux kernel maintainers expect bug reporters to be able to follow up on
142 never follow up on a request to try out a fix.
145 on a supported kernel, even if you can't follow up with retests. Follow
|
| D | COPYING | 73 modification follow.
|
| D | MAINTAINERS | 5 Please try to follow the guidelines below. This will make things
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/panel/ |
| D | display-timing.txt | 39 All the optional properties that are not bool follow the following logic:
|
| /linux-4.4.14/drivers/isdn/gigaset/ |
| D | Kconfig | 12 one of the connection specific parts that follow.
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | README.vbi | 23 'itv0': After this magic number two unsigned longs follow. Bits 0-17 of the first
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | arch_timer.txt | 33 systems which follow the ARMv7 architected reset values.
|
| D | arm,scpi.txt | 65 The rest of the properties should follow the generic mmio-sram description
|
| D | cci.txt | 14 Bindings for the CCI node follow the ePAPR standard, available from:
|
| D | topology.txt | 87 cpu-map child nodes must follow a naming convention where the node name
|
| D | cpus.txt | 9 Bindings for CPU nodes follow the ePAPR v1.1 standard, available from:
|
| D | idle-states.txt | 259 The state node name shall follow standard device tree naming
|
| /linux-4.4.14/Documentation/devicetree/bindings/edac/ |
| D | apm-xgene-edac.txt | 4 The follow error types are supported:
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | sh_mobile_ceu_camera.txt | 118 We choose to follow the advise and interpret cropping units as client input
|
| /linux-4.4.14/Documentation/thermal/ |
| D | nouveau_thermal | 81 Bug reports should be filled on Freedesktop's bug tracker. Please follow
|
| /linux-4.4.14/Documentation/EDID/ |
| D | HOWTO.txt | 5 either correctly working because all components follow the standards -
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | overlay-notes.txt | 127 /* more fragments follow */
|
| D | booting-without-of.txt | 131 doesn't follow them properly. In addition, since the advent of the
706 and there exist an OF bus binding, then you should follow the
804 practice to follow the standard and its evolutions as closely as
1233 nodes should follow these specifications, except where noted in this
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | dmatest.txt | 91 The details of a data miscompare error are also emitted, but do not follow the
|
| /linux-4.4.14/Documentation/acpi/ |
| D | method-customizing.txt | 55 insert and then follow the step c) ~ g) in section 1.
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.sc | 186 - please open the isdn-hdlc file in the examples directory and follow along...
211 - please open the isdn-ppp file in the examples directory and follow along...
236 - please open the isdn-mppp file in the examples directory and follow along...
|
| D | INTERFACE.fax | 109 0: output OK message (more pages follow)
|
| D | README.act2000 | 8 However MCA and PCMCIA will follow soon.
|
| /linux-4.4.14/Documentation/acpi/apei/ |
| D | output_format.txt | 5 format is as follow.
|
| /linux-4.4.14/Documentation/usb/ |
| D | gadget_printer.txt | 42 The follow command line parameter can be used when loading the printer gadget
85 2) compile the code with the follow command:
|
| D | usbmon.txt | 169 - Data words follow, in big endian hexadecimal format. Notice that they are
|
| D | usb-serial.txt | 114 To use Pocket IE, follow the instructions given at
|
| D | gadget-testing.txt | 165 available in the system. Once a "device" is available, the user should follow
|
| /linux-4.4.14/arch/arm/kernel/ |
| D | entry-armv.S | 1051 @ the branch table must immediately follow this code
1062 @ handler addresses follow this label
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | nfs-rdma.txt | 80 Uncompress the package and follow the installation instructions.
197 For other device types, follow the appropriate procedures.
|
| /linux-4.4.14/arch/alpha/kernel/ |
| D | osf_sys.c | 609 long follow; member
620 long follow; member
635 long follow; member
|
| /linux-4.4.14/include/uapi/linux/ |
| D | coda.h | 724 int follow; member
|
| /linux-4.4.14/Documentation/vm/ |
| D | active_mm.txt | 14 > wasn't able to follow linux-kernel for a while).
|
| D | numa_memory_policy.txt | 125 private mappings that have not yet been written by the task, follow
203 allocation will follow the per node zonelist.
|
| D | slub.txt | 207 Various types of lines can follow the BUG SLUB line:
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | TODO | 88 2) follow_link and readdir code does not follow dfs junctions
|
| D | README | 57 If you have built the CIFS vfs into the kernel itself, follow the instructions
|
| D | CHANGES | 472 as directories rather than symlinks because we can do follow link on them.
|
| /linux-4.4.14/Documentation/fb/ |
| D | pxafb.txt | 106 Applications should follow the sequence below to operate an overlay
|
| D | modedb.txt | 150 BTW, only a few fb drivers use this at the moment. Others are to follow
|
| /linux-4.4.14/drivers/staging/unisys/Documentation/ |
| D | proc-entries.txt | 61 The entries in proc for these modules all follow the same
|
| /linux-4.4.14/Documentation/x86/ |
| D | exception-tables.txt | 56 as an example. The definition is somewhat hard to follow, so let's peek at
125 WOW! Black GCC/assembly magic. This is impossible to follow, so let's
|
| D | intel_mpx.txt | 170 The _sigfault feild of struct siginfo is extended as follow:
|
| D | boot.txt | 688 as follow:
1005 LOADLIN, which runs under DOS) it may be impossible to follow the
1044 follow:
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-st.txt | 98 pin-functions nodes follow...
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ChangeLog.arcmsr | 55 ** follow Randy.Danlup kindness suggestion cleanup this code
|
| D | ncr53c8xx.txt | 277 will set tagged commands queue depths as follow:
301 setting verbose level to zero, as follow:
705 will set devices queue depth as follow:
848 iarb:#x use this feature according to bit fields as follow:
950 data format used, as follow:
974 to ignore some options configured in the NVRAM, as follow:
|
| D | sym53c8xx_2.txt | 248 will set tagged commands queue depths as follow:
272 setting verbose level to zero, as follow:
707 data format used, as follow:
|
| D | LICENSE.qla4xxx | 68 modification follow.
|
| D | LICENSE.qla2xxx | 69 modification follow.
|
| D | BusLogic.txt | 376 be probed, but the probe order will always follow the standard list.
|
| D | ChangeLog.lpfc | 1056 * Arranging lpfc_scsiport.c to follow style of use after
|
| /linux-4.4.14/Documentation/networking/ |
| D | radiotap-headers.txt | 41 After the fixed part of the header, the arguments follow for each argument
|
| D | ltpc.txt | 101 Instead, you follow the same procedure as for doing IP in EtherTalk.
|
| D | iphase.txt | 39 To install the ATM adapters in the system, follow the steps below.
|
| D | openvswitch.txt | 151 compatibility for applications that follow the rules listed under
223 indicating that a VLAN TCI should follow, but which is truncated just
|
| D | phonet.txt | 119 Phonet resources, as follow:
|
| D | netconsole.txt | 92 Some examples follow (where configfs is mounted at the /sys/kernel/config
|
| D | ipvs-sysctl.txt | 120 the automatic mode, the rate is determined by the follow
|
| D | README.sb1000 | 50 To make the SB1000 card work, follow these steps:
|
| D | spider_net.txt | 79 of the descrs that follow.
|
| D | LICENSE.qlcnic | 67 modification follow.
|
| D | LICENSE.qlge | 67 modification follow.
|
| D | filter.txt | 81 follow-up example) is being passed to the kernel through setsockopt(2).
379 support (follow-up example commands starting with '>' denote bpf_dbg shell).
|
| D | cs89x0.txt | 62 The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
|
| D | bonding.txt | 33 who to ask for help, please follow the links at the end of this file.
469 follow or 2
471 The "follow" fail_over_mac policy causes the MAC
493 This option was added in bonding version 3.2.0. The "follow"
|
| D | ip-sysctl.txt | 728 pressure: This value was introduced to follow format of tcp_mem.
1898 pressure: This value was introduced to follow format of tcp_mem.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | rcu.txt | 62 o What guidelines should I follow when writing code that uses RCU?
|
| D | rcu_dereference.txt | 144 misordering will not affect the accesses that follow
|
| D | checklist.txt | 402 that readers can follow that could be affected by the
|
| D | whatisRCU.txt | 439 See checklist.txt for additional rules to follow when using RCU.
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | lis3lv02d | 92 into free space, follow the fall with your hands for like 10
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | s2mps11.txt | 69 Grouping of BUCKs sharing ramp rate setting is as follow : BUCK[1, 6],
|
| /linux-4.4.14/Documentation/ide/ |
| D | ChangeLog.ide-tape.1995-2002 | 187 * 3 : 2+follow all chrdev related procedures
188 * 4 : 3+follow all procedures
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | Channel-Mapping-API.txt | 133 don't follow the standard definition above but driver-specific.
|
| /linux-4.4.14/Documentation/i2c/ |
| D | fault-codes | 34 Also, codes returned by adapter probe methods follow rules which are
|
| /linux-4.4.14/arch/unicore32/kernel/ |
| D | entry.S | 713 @ the branch table must immediately follow this code
722 @ handler addresses follow this label
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-record.txt | 79 Event filter. This option should follow a event selector (-e) which
84 Don't record events issued by perf itself. This option should follow
|
| /linux-4.4.14/Documentation/gpio/ |
| D | sysfs.txt | 96 for "rising" and "falling" edges will follow this
|
| D | driver.txt | 230 The following is a checklist to follow when preparing a driver for real
|
| D | gpio-legacy.txt | 716 for "rising" and "falling" edges will follow this
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | verity.txt | 131 It only reads the hash blocks which directly follow the header.
|
| D | cache.txt | 248 #feature args : Number of feature args to follow
254 #policy args : Number of policy arguments to follow (must be even)
|
| D | dm-raid.txt | 42 <#raid_params>: The number of parameters that follow.
|
| /linux-4.4.14/Documentation/console/ |
| D | console.txt | 110 console drivers must follow these guidelines:
|
| /linux-4.4.14/arch/m68k/math-emu/ |
| D | fp_scan.S | 342 | Instructions follow
|
| /linux-4.4.14/Documentation/hid/ |
| D | hid-transport.txt | 87 HID core requires transport drivers to follow a given design. A Transport
153 on devices that follow the HID specs except during device initialization to
|
| /linux-4.4.14/Documentation/input/ |
| D | gamepad.txt | 63 All gamepads that follow the protocol described here map BTN_GAMEPAD. This is
|
| D | event-codes.txt | 130 with current userspace it is recommended to follow this distinction. In the
|
| /linux-4.4.14/arch/powerpc/platforms/44x/ |
| D | Kconfig | 105 See http://www.pikatechnologies.com/ and follow the "PIKA for Computer
|
| /linux-4.4.14/Documentation/arm64/ |
| D | arm-acpi.txt | 3 ACPI can be used for ARMv8 general purpose servers designed to follow
325 The kernel ACPI code will also assume that the _PSx methods follow the normal
442 It is the intent of the ARMv8 ACPI kernel code to follow the ACPI specification
|
| /linux-4.4.14/Documentation/pps/ |
| D | pps.txt | 176 and the run ppstest as follow:
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | rk3288-veyron.dtsi | 234 * make it easier to follow the schematic. The signals
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 31 It is *strongly* recommended that 5200B device trees follow this convention
|
| /linux-4.4.14/net/ipv6/netfilter/ |
| D | Kconfig | 131 for IPv6 use this, but connection tracking is going to follow.
|
| /linux-4.4.14/arch/parisc/kernel/ |
| D | perf_asm.S | 59 sync ; follow ERS
|
| /linux-4.4.14/Documentation/wimax/ |
| D | README.i2400m | 106 To load the driver, follow the instructions in the install section;
|
| /linux-4.4.14/Documentation/power/ |
| D | suspend-and-cpuhotplug.txt | 25 More details follow:
|
| D | basic-pm-debugging.txt | 199 Next, you can follow the instructions at S2RAM_LINK to test the system, but if
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | platform.txt | 35 Platform drivers follow the standard driver model convention, where
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | do_func.S | 64 | Check for fmovecr. It does not follow the format of fp gen
|
| D | round.S | 285 | therefore do not have the easy to follow decrement/shift loop.
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | spkguide.txt | 642 follow these steps to use it.
869 string of characters that follow the word echo. If you were to just
1036 The files under the i18n subdirectory all follow the same format.
1167 Any arguments that follow the name of the daemon are passed to the daemon
1308 number of copies you must also follow the conditions in section 3.
1467 the collection, provided that you follow the rules of this License for
1472 License into the extracted document, and follow this License in all
|
| /linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/ |
| D | gpc.fuc | 400 // on save it means: "a load will follow this save"
|
| D | hub.fuc | 596 // on save it means: "a load will follow this save"
|
| /linux-4.4.14/Documentation/s390/ |
| D | 3270.txt | 124 should follow these steps:
|
| D | Debugging390.txt | 406 Note: To follow stackframes requires a knowledge of C or Pascal &
768 So if you have an objdump listing by hand, it is quite easy to follow, and if
1085 & cannot follow the flow of code but you know it isn't smp related.
1217 should be able to sniff further back if you follow the following tricks.
|
| D | s390dbf.txt | 482 to follow the correct pointers of the data-structures defined
|
| /linux-4.4.14/arch/xtensa/ |
| D | Kconfig | 216 not to follow Tensilica's recommendation.
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | ioctl-number.txt | 38 long as it is unique. Some devices are irregular and don't follow any
|
| /linux-4.4.14/Documentation/rapidio/ |
| D | rapidio.txt | 78 RapidIO device-specific drivers follow Linux Kernel Driver Model and are
|
| /linux-4.4.14/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 276 Details of the allowable transitions follow.
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | fscache.txt | 70 FS-Cache does not follow the idea of completely loading every netfs file
|
| D | backend-api.txt | 326 attr_changed operation should be performed. The caller will follow up
|
| /linux-4.4.14/Documentation/timers/ |
| D | NO_HZ.txt | 243 Clone this archive and follow the instructions in the README file.
|
| /linux-4.4.14/Documentation/serial/ |
| D | moxa-smartio | 273 completed, follow the below step.
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 240 * initiator. We follow the guidlines from section 6.5
267 * immediately follow the identify. We test for a valid
941 * complete) that usually follow a data phase.
|
| D | aic79xx.seq | 1703 * complete) that usually follow a data phase.
|
| /linux-4.4.14/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 107 follow all sysfs guidelines and correctly process all errors (the sysfs
860 Most (newer?) models seem to follow this pattern:
907 subsystem, and follow all of the hwmon guidelines at
|
| /linux-4.4.14/drivers/staging/rtl8192u/ |
| D | copying | 57 modification follow.
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | kernel-api.xml.db | 215 API-follow-pfn
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | blkio-controller.txt | 394 correctly follow the resource restrictions imposed by both memory and
|
| D | cpusets.txt | 556 -1 : no request. use system default or follow request of others.
|
| /linux-4.4.14/tools/usb/usbip/ |
| D | COPYING | 57 modification follow.
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-error-recovery.txt | 112 event will be platform-dependent, but will follow the general
|
| D | pci.txt | 55 the driver needs to take the follow steps:
|
| /linux-4.4.14/drivers/staging/rtl8192e/ |
| D | license | 62 follow.
|
| /linux-4.4.14/fs/ |
| D | namei.c | 1707 int follow, in should_follow_link() argument
1712 if (!follow) in should_follow_link()
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 4.Coding | 106 code which is easier to follow.
|
| D | 2.Process | 402 - Do not try to follow every conversation - nobody else does. It is
|
| /linux-4.4.14/arch/x86/crypto/ |
| D | aesni-intel_asm.S | 56 # more specifically, ALL_F should follow SHIFT_MASK,
57 # and ZERO should follow ALL_F
|
| D | aesni-intel_avx-x86_64.S | 133 # more specifically, ALL_F should follow SHIFT_MASK, and ZERO should follow ALL_F
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 33 parity bit is even. (see wikipedia if you can't follow this).
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 4061 follow the instructions contained therein.
4156 If the panic was 'segfault in signals', then follow the instructions
|
| /linux-4.4.14/Documentation/block/ |
| D | biodoc.txt | 970 All requests seen by I/O schedulers strictly follow one of the following three
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.OSS | 939 was listed in the beginning of this file. In this case you should follow
|