Searched full:practice (Results 1 – 25 of 369) sorted by relevance
12345678910>>...15
/linux-5.10/Documentation/maintainer/ |
D | modifying-patches.rst | 23 This practice is particularly helpful if you maintain a stable branch and 29 Special note to back-porters: It seems to be a common and useful practice
|
D | configure-git.rst | 42 of patches here is a recommended practice, and when a maintainer applies a
|
/linux-5.10/Documentation/networking/ |
D | netif-msg.rst | 13 constrained by backwards compatibility previous practice. It is useful 15 practice and relate it to older driver source code.
|
D | ipsec.rst | 35 Current IPComp implementation is indeed by the book, while as in practice
|
/linux-5.10/Documentation/devicetree/bindings/pci/ |
D | pci.txt | 8 Open Firmware Recommended Practice: Interrupt Mapping 9 https://www.devicetree.org/open-firmware/practice/imap/imap0_9d.pdf
|
/linux-5.10/Documentation/livepatch/ |
D | cumulative-patches.rst | 67 A good practice is to set .replace flag in any released livepatch. 101 A good practice might be to remove shadow variables in the post-unpatch
|
/linux-5.10/fs/nfs/ |
D | io.c | 35 * In practice, this means that buffered read operations are allowed to 115 * In practice, this means that direct I/O operations are allowed to
|
/linux-5.10/Documentation/admin-guide/ |
D | unicode.rst | 52 U+F0FF, emulating the previous behaviour. In practice, this range 110 Unicode practice. 125 Unicode practice these differences are considered font variants.
|
/linux-5.10/crypto/asymmetric_keys/ |
D | tpm.asn1 | 3 -- http://david.woodhou.se/draft-woodhouse-cert-best-practice.html#I-D.mavrogiannopoulos-tpmuri
|
/linux-5.10/fs/ceph/ |
D | io.c | 43 * In practice, this means that buffered read operations are allowed to 129 * In practice, this means that direct I/O operations are allowed to
|
/linux-5.10/Documentation/devicetree/bindings/usb/ |
D | nvidia,tegra20-ehci.txt | 5 Practice : Universal Serial Bus" with the following modifications
|
/linux-5.10/Documentation/userspace-api/media/v4l/ |
D | common.rst | 23 In practice most steps are optional and can be executed out of order. It
|
/linux-5.10/tools/lib/bpf/ |
D | libbpf_common.h | 27 * bytes, but that's the best way I've found and it seems to work in practice.
|
/linux-5.10/Documentation/i2c/busses/ |
D | i2c-taos-evm.rst | 48 practice, as these modules are meant for evaluation and testing only.
|
/linux-5.10/fs/xfs/ |
D | xfs_export.h | 45 * practice this means when exporting an XFS filesystem with 64bit
|
/linux-5.10/Documentation/devicetree/bindings/gpio/ |
D | gpio.txt | 40 drain. This is the recommended practice. 236 GPIO and other functions. It is a fairly common practice among silicon 258 in practice these ranges are often lumped in discrete sets.
|
/linux-5.10/arch/powerpc/include/asm/ |
D | synch.h | 33 * POWER9 in practice does not need this, because address spaces with in ppc_after_tlbiel_barrier()
|
/linux-5.10/drivers/iio/ |
D | industrialio-triggered-event.c | 24 * completely initialized, but not yet registered. In practice this means that
|
/linux-5.10/include/acpi/platform/ |
D | acintel.h | 14 * Use compiler specific <stdarg.h> is a good practice for even when
|
D | acgcc.h | 14 * Use compiler specific <stdarg.h> is a good practice for even when
|
/linux-5.10/include/linux/ |
D | fs_types.h | 8 * bits are specific to every file system, in practice, many
|
/linux-5.10/Documentation/timers/ |
D | hrtimers.rst | 11 such high-resolution timer implementations in practice, we came to the 176 code got a healthy amount of testing and use in practice.
|
/linux-5.10/arch/arm64/kernel/ |
D | perf_regs.c | 34 * how well that works in practice, somebody might be relying on it. in perf_reg_value()
|
/linux-5.10/Documentation/scsi/ |
D | scsi.rst | 25 unloaded. In practice the modprobe and rmmod commands (and "autoclean")
|
/linux-5.10/arch/arm64/kernel/vdso/ |
D | sigreturn.S | 47 * the frame pointer and the link register here; in practice, this is likely to
|
12345678910>>...15