Home
last modified time | relevance | path

Searched full:practice (Results 1 – 25 of 395) sorted by relevance

12345678910>>...16

/Linux-v5.15/Documentation/maintainer/
Dmodifying-patches.rst23 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
Dconfigure-git.rst42 of patches here is a recommended practice, and when a maintainer applies a
/Linux-v5.15/Documentation/networking/
Dnetif-msg.rst13 constrained by backwards compatibility previous practice. It is useful
15 practice and relate it to older driver source code.
Dipsec.rst35 Current IPComp implementation is indeed by the book, while as in practice
/Linux-v5.15/Documentation/livepatch/
Dcumulative-patches.rst67 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-v5.15/Documentation/devicetree/bindings/pci/
Dpci.txt8 Open Firmware Recommended Practice: Interrupt Mapping
9 https://www.devicetree.org/open-firmware/practice/imap/imap0_9d.pdf
/Linux-v5.15/fs/nfs/
Dio.c35 * 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-v5.15/Documentation/admin-guide/
Dunicode.rst52 U+F0FF, emulating the previous behaviour. In practice, this range
110 Unicode practice.
125 Unicode practice these differences are considered font variants.
/Linux-v5.15/crypto/asymmetric_keys/
Dtpm.asn13 -- http://david.woodhou.se/draft-woodhouse-cert-best-practice.html#I-D.mavrogiannopoulos-tpmuri
/Linux-v5.15/fs/ceph/
Dio.c43 * 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-v5.15/Documentation/devicetree/bindings/usb/
Dnvidia,tegra20-ehci.txt5 Practice : Universal Serial Bus" with the following modifications
/Linux-v5.15/tools/lib/bpf/
Dlibbpf_common.h27 * bytes, but that's the best way I've found and it seems to work in practice.
/Linux-v5.15/Documentation/userspace-api/media/v4l/
Dcommon.rst23 In practice most steps are optional and can be executed out of order. It
/Linux-v5.15/Documentation/i2c/busses/
Di2c-taos-evm.rst48 practice, as these modules are meant for evaluation and testing only.
/Linux-v5.15/fs/xfs/
Dxfs_export.h45 * practice this means when exporting an XFS filesystem with 64bit
/Linux-v5.15/Documentation/devicetree/bindings/gpio/
Dgpio.txt40 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-v5.15/arch/powerpc/include/asm/
Dsynch.h33 * POWER9 in practice does not need this, because address spaces with in ppc_after_tlbiel_barrier()
/Linux-v5.15/drivers/iio/
Dindustrialio-triggered-event.c24 * completely initialized, but not yet registered. In practice this means that
/Linux-v5.15/include/linux/
Dfs_types.h8 * bits are specific to every file system, in practice, many
Drcu_node_tree.h29 * In practice, this did work well going from three levels to four.
/Linux-v5.15/include/acpi/platform/
Dacintel.h14 * Use compiler specific <stdarg.h> is a good practice for even when
/Linux-v5.15/Documentation/timers/
Dhrtimers.rst11 such high-resolution timer implementations in practice, we came to the
176 code got a healthy amount of testing and use in practice.
/Linux-v5.15/drivers/iio/accel/
Dbmc150-accel.h25 * in practice (e.g. for device tree platforms).
/Linux-v5.15/Documentation/scsi/
Dscsi.rst25 unloaded. In practice the modprobe and rmmod commands (and "autoclean")
/Linux-v5.15/arch/arm64/kernel/
Dperf_regs.c34 * how well that works in practice, somebody might be relying on it. in perf_reg_value()

12345678910>>...16