| /linux-4.1.27/Documentation/sysctl/ |
| D | README | 54 one part of the kernel, so you can do configuration on a piece
55 by piece basis, or just some 'thematic frobbing'.
|
| /linux-4.1.27/Documentation/mn10300/ |
| D | ABI.txt | 76 this will point to a piece of memory large enough to hold the result of the
77 function. In this case, the callee will return the value in that piece of
|
| /linux-4.1.27/security/keys/ |
| D | keyring.c | 177 u32 piece; in hash_key_type_and_desc() local
191 piece = 0; in hash_key_type_and_desc()
192 memcpy(&piece, description, n); in hash_key_type_and_desc()
195 acc = mult_64x32_and_fold(acc, piece); in hash_key_type_and_desc()
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,saw2.txt | 5 power-controller that transitions a piece of hardware (like a processor or
|
| /linux-4.1.27/Documentation/fb/ |
| D | internals.txt | 46 particular piece of hardware.
|
| /linux-4.1.27/drivers/char/ipmi/ |
| D | Kconfig | 37 You can fetch these events and use the sequence numbers to piece the
|
| /linux-4.1.27/Documentation/video4linux/bttv/ |
| D | README.freeze | 70 it share the IRQ with some other piece of hardware. IRQ sharing with
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci-iov-howto.txt | 73 Following piece of code illustrates the usage of the SR-IOV API.
|
| /linux-4.1.27/Documentation/power/ |
| D | s2ram.txt | 68 Reason for this is that the RTC is the only reliably available piece of
|
| D | freezing-of-tasks.txt | 206 First of all, grabbing the 'pm_mutex' lock to mutually exclude a piece of code
208 If possible, that piece of code must instead hook onto the suspend/hibernation
|
| /linux-4.1.27/drivers/char/tpm/ |
| D | Kconfig | 15 userspace enablement piece of the specification, can be
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 3.Early-stage | 14 easy: when a driver is needed for a specific piece of hardware, for
155 track down a maintainer for a specific piece of code.
|
| D | 7.AdvancedTopics | 158 piece of advice for reviewers (all reviewers) is this: phrase review
|
| D | 4.Coding | 47 avoided. It is natural to fix the style of a piece of code while working
319 The first piece of documentation for any patch is its associated
|
| /linux-4.1.27/Documentation/ |
| D | DMA-ISA-LPC.txt | 40 In order to allocate a piece of memory that satisfies all these
|
| D | lzo.txt | 27 as a piece of information for next instructions.
|
| D | memory-barriers.txt | 470 there won't be any such interaction in any particular piece of code, then
471 memory barriers are unnecessary in that piece of code.
499 (*) There is no guarantee that some intervening piece of off-the-CPU
1682 As an example, consider a piece of code that marks an object as being dead
2248 be a problem as a single-threaded linear piece of code will still appear to
2273 queued on the semaphore, by virtue of it having a piece of its stack linked to
2872 given the following piece of code to execute:
2913 So what another CPU, say, might actually observe from the above piece of code
|
| D | DMA-API.txt | 195 Maps a piece of processor virtual memory so it can be accessed by the
211 contiguous piece of memory. For this reason, memory to be mapped by
|
| D | IPMI.txt | 95 ipmi_msghandler - This is the central piece of software for the IPMI
255 piece of data, the handler_data, that will be passed back to you on
|
| D | assoc_array.txt | 484 Shortcuts are metadata records that jump over a piece of keyspace. A shortcut
|
| D | xillybus.txt | 38 An FPGA (Field Programmable Gate Array) is a piece of logic hardware, which
|
| D | kprobes.txt | 114 is an arbitrary piece of code -- typically just a nop instruction.
|
| D | DMA-API-HOWTO.txt | 111 The first piece of information you must know is what kernel memory can
|
| D | pinctrl.txt | 19 - A pin controller is a piece of hardware, usually a set of registers, that
|
| /linux-4.1.27/Documentation/trace/ |
| D | mmiotrace.txt | 94 "pciid" and "nick" with the PCI ID or model name of your piece of hardware
|
| D | ftrace-design.txt | 165 more information). The only architecture-specific piece in it is the setup of
|
| /linux-4.1.27/Documentation/acpi/ |
| D | enumeration.txt | 76 acpi_dma_spec into the corresponding DMA channel. A piece of code for that case
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.concap | 52 negotiation before the first piece of user data can be transmitted.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | squashfs.txt | 251 particular piece of metadata or fragment will retrieve other metadata/fragments
|
| D | proc.txt | 75 and helped create a great piece of software... :)
|
| /linux-4.1.27/Documentation/networking/ |
| D | README.sb1000 | 8 a great deal of thanks for this wonderful piece of code!
|
| D | rxrpc.txt | 630 to collect as it arrives. All but the last piece of the request data will
|
| /linux-4.1.27/scripts/ |
| D | spelling.txt | 693 peice||piece
|
| /linux-4.1.27/Documentation/usb/ |
| D | gadget-testing.txt | 456 It is not possible to test the SOCK_STREAM protocol without a specific piece
|
| /linux-4.1.27/firmware/ |
| D | WHENCE | 6 if known, for each piece of firmware distributed for use with the Linux
|
| /linux-4.1.27/Documentation/laptops/ |
| D | laptop-mode.txt | 209 this on powerbooks too. I hope that this is a piece of information that
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 1264 additional piece of information will be set in the flags bitmap.
2480 Gets/sets a specified piece of device configuration and/or state. The
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 1205 exist on a single piece of silicon. For these SOCs, an SOC node
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | spkguide.txt | 686 chosen software synthesizer, you still need one more piece of software
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 3390 It's not stack overflow. The only "stack-like" piece of this data is
|