| /linux/Documentation/admin-guide/sysctl/ |
| H A D | index.rst | 62 one part of the kernel, so you can do configuration on a piece
63 by piece basis, or just some 'thematic frobbing'.
|
| /linux/security/keys/ |
| H A D | keyring.c | 169 u32 piece; in hash_key_type_and_desc() local
176 piece = (unsigned long)index_key->domain_tag; in hash_key_type_and_desc()
177 acc = mult_64x32_and_fold(acc, piece); in hash_key_type_and_desc()
186 piece = 0; in hash_key_type_and_desc()
187 memcpy(&piece, description, n); in hash_key_type_and_desc()
190 acc = mult_64x32_and_fold(acc, piece); in hash_key_type_and_desc()
|
| /linux/Documentation/misc-devices/ |
| H A D | tps6594-pfsm.rst | 13 hardware. It is a piece of code.
|
| /linux/Documentation/fb/ |
| H A D | internals.rst | 52 particular piece of hardware.
|
| /linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 58 When there are multiple maintainers for a piece of code an ``Acked-by``
121 for any piece of code, no matter how trivial. It spreads the burden, helps
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | using-gpio.rst | 24 industrial automation, PLC-type use cases, door controllers, in short a piece
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | usage.rst | 32 An *expectation* specifies that we expect a piece of code to do something in a
34 expectations about the behavior of a piece of code under test. When one or more
224 piece of hardware.
316 In order to unit test a piece of code that calls a method in a class, the
320 A fake class implements a piece of code that is different than what runs in a
|
| H A D | faq.rst | 56 test to test the interaction between a driver and a piece of hardware, or to
|
| /linux/Documentation/power/ |
| H A D | s2ram.rst | 70 Reason for this is that the RTC is the only reliably available piece of
|
| H A D | freezing-of-tasks.rst | 230 piece of code from system-wide sleep such as suspend/hibernation is not
231 encouraged. If possible, that piece of code must instead hook onto the
|
| /linux/Documentation/PCI/ |
| H A D | pci-iov-howto.rst | 109 Following piece of code illustrates the usage of the SR-IOV API.
|
| /linux/fs/proc/ |
| H A D | Kconfig | 121 this interface. For example, rkt is such a piece of software.
|
| /linux/Documentation/process/ |
| H A D | 3.Early-stage.rst | 18 easy: when a driver is needed for a specific piece of hardware, for
164 track down a maintainer for a specific piece of code.
|
| /linux/Documentation/core-api/ |
| H A D | dma-isa-lpc.rst | 41 In order to allocate a piece of memory that satisfies all these
|
| H A D | genalloc.rst | 87 how the allocation functions choose which specific piece of memory to
|
| H A D | padata.rst | 162 piece of the job that one thread completes in one call to the thread function.
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | transhuge.rst | 560 piece without splitting.
588 piece without splitting.
592 swap device in one piece.
606 swap device in one piece without splitting.
|
| /linux/drivers/char/ipmi/ |
| H A D | Kconfig | 50 sequence numbers to piece the string together. This config
|
| /linux/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 91 A set of electronic circuits on one small flat piece of
|
| /linux/Documentation/gpu/amdgpu/ |
| H A D | driver-core.rst | 118 piece of memory and then put a pointer to the memory into the queue.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | v4l2.rst | 374 Somehow a piece of junk slipped into the capture example, removed.
|
| H A D | colorspaces.rst | 105 The final piece that defines a colorspace is a function that transforms
|
| /linux/Documentation/trace/ |
| H A D | mmiotrace.rst | 113 "pciid" and "nick" with the PCI ID or model name of your piece of hardware
|
| /linux/drivers/char/tpm/ |
| H A D | Kconfig | 18 userspace enablement piece of the specification, can be
|
| /linux/Documentation/staging/ |
| H A D | lzo.rst | 29 as a piece of information for next instructions.
|