| /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/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/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/drivers/crypto/axis/ |
| H A D | artpec6_crypto.c | 397 size_t piece; in artpec6_crypto_walk_advance() local
401 piece = min(nbytes, (size_t)awalk->sg->length - awalk->offset); in artpec6_crypto_walk_advance()
402 nbytes -= piece; in artpec6_crypto_walk_advance()
403 awalk->offset += piece; in artpec6_crypto_walk_advance()
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | faq.rst | 56 test to test the interaction between a driver and a piece of hardware, or to
|
| /linux/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 91 A set of electronic circuits on one small flat piece of
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | transhuge.rst | 616 piece without splitting.
644 piece without splitting.
648 swap device in one piece.
662 swap device in one piece without splitting.
|
| /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/Documentation/userspace-api/media/v4l/ |
| H A D | v4l2.rst | 375 Somehow a piece of junk slipped into the capture example, removed.
|
| H A D | colorspaces.rst | 106 The final piece that defines a colorspace is a function that transforms
|
| /linux/Documentation/staging/ |
| H A D | lzo.rst | 29 as a piece of information for next instructions.
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | access-coordinates.rst | 21 :doc:`HMAT <../platform/acpi/hmat>` subtable. This piece represents the
|
| /linux/drivers/char/tpm/ |
| H A D | Kconfig | 18 userspace enablement piece of the specification, can be
|
| /linux/Documentation/ |
| H A D | memory-barriers.txt | 520 there won't be any such interaction in any particular piece of code, then
521 memory barriers are unnecessary in that piece of code.
549 (*) There is no guarantee that some intervening piece of off-the-CPU
1901 As an example, consider a piece of code that marks an object as being dead
2353 be a problem as a single-threaded linear piece of code will still appear to
2378 queued on the semaphore, by virtue of it having a piece of its stack linked to
2798 given the following piece of code to execute:
2839 So what another CPU, say, might actually observe from the above piece of code
|
| /linux/Documentation/bpf/ |
| H A D | ringbuf.rst | 92 array/hash maps. Once ready, this piece of memory is either committed or
|
| /linux/Documentation/driver-api/ |
| H A D | ntb.rst | 38 Primary purpose of NTB is to share some piece of memory between at least two
|