| /linux/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 103 All involved developers pledge to adhere to the embargo rules and to keep
109 hardware security team will inform the involved parties immediately. If you
145 response team, but is not necessarily involved in the mitigation
196 kernel developer community as needed. Any involved party can suggest
257 The involved parties will negotiate the date and time when the embargo
265 required for all involved parties to develop, test, and prepare their
268 involved developers and response teams as the patches need to be kept up to
285 reporting process and further handling. Ambassadors are not involved in the
287 an involved disclosed party. The current ambassadors list:
|
| H A D | researcher-guidelines.rst | 9 kernel, the activities involved in producing it, and any other byproducts
15 involves security. Getting involved early helps both improve the quality
44 involved. Developers cannot be interacted with/experimented on without
|
| H A D | code-of-conduct-interpretation.rst | 18 kernel. Know that this happens because everyone involved wants to see
63 and the technical complexity involved naturally require expertise and
189 these reports, working with all involved parties.
|
| H A D | 2.Process.rst | 7 with relatively small numbers of users and developers involved. With a
8 user base in the millions and with some 2,000 developers involved over the
144 kernel. There is, instead, a somewhat involved (if somewhat informal)
207 involved.
427 the Cc: header for all involved. In the absence of a strong reason (such
|
| H A D | adding-syscalls.rst | 7 This document describes what's involved in adding a new system call to the
21 - If the operations involved can be made to look like a filesystem-like
453 If there's a pointer-to-a-pointer involved, the decision is easy: x32 is
462 If no pointers are involved, then it is preferable to re-use the 64-bit system
466 In either case, you should check that the types involved in your argument
|
| H A D | 3.Early-stage.rst | 34 stability. Their preferred solutions involved realtime scheduling access
201 of a kernel development project, the better off everybody involved will be.
|
| H A D | 8.Conclusion.rst | 72 everybody involved wins. Fire up your editor and come join us; you will be
|
| /linux/arch/um/ |
| H A D | Kconfig.debug | 13 If you're involved in UML kernel development and want to use gprof,
28 If you're involved in UML kernel development and want to use gcov,
|
| /linux/sound/soc/sof/ |
| H A D | Kconfig | 80 Say Y if you are involved in SOF development and need this option.
93 Say Y if you are involved in SOF development and need this option.
126 If you are not involved in SOF releases and CI development,
137 Say Y if you are involved in SOF development and need this option.
|
| /linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 62 * lock the subdirectories involved (exclusive), source before target.
63 * lock the non-directories involved (exclusive), in inode pointer order.
93 we'd been looking for. No extra locking is involved in these two cases.
209 has acquired filesystem lock and verified that directories involved have
220 children must be involved and thus neither of them could be a descendent
|
| /linux/Documentation/driver-api/crypto/ |
| H A D | index.rst | 7 Documentation for crypto drivers that may need more involved setup and
|
| /linux/Documentation/power/ |
| H A D | suspend-and-cpuhotplug.rst | 18 the locking involved. It outlines the notifications involved as well.
173 II. What are the issues involved in CPU hotplug?
|
| /linux/arch/arm/mach-mmp/ |
| H A D | platsmp.c | 17 * there. No IPIs involved. in mmp3_boot_secondary()
|
| /linux/include/linux/mmc/ |
| H A D | pm.h | 16 * abstractions involved, from the host controller driver, to the MMC core
|
| /linux/Documentation/core-api/irq/ |
| H A D | concepts.rst | 24 of the hardware involved. The ISA IRQs are a classic example of
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | super.rst | 371 - inode involved in first error.
375 - Number of block involved of first error.
391 - inode involved in most recent error.
399 - Number of block involved in most recent error.
|
| /linux/Documentation/arch/loongarch/ |
| H A D | booting.rst | 25 All pointers involved at this stage are in physical addresses.
|
| /linux/Documentation/arch/arm/samsung/ |
| H A D | overview.rst | 53 where to simplify the include and dependency issues involved with having
|
| /linux/Documentation/mhi/ |
| H A D | topology.rst | 16 It is however not involved in the actual data transfer as the data transfer
|
| /linux/arch/mips/include/asm/dec/ |
| H A D | ecc.h | 23 #define KN0X_EAR_ADDRESS (0x7ffffff<<0) /* address involved */
|
| /linux/arch/arm/include/asm/ |
| H A D | highmem.h | 30 * the locking involved must also disable IRQs which is incompatible with
|
| /linux/Documentation/arch/s390/ |
| H A D | qeth.rst | 44 if no VLAN is involved in the event.
|
| /linux/Documentation/arch/powerpc/ |
| H A D | cpu_features.rst | 27 Implementing cpufeatures in assembly is a little more involved. There are
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | attack_vector_controls.rst | 36 The kernel data involved might be limited to certain kernel memory, or include
75 hypervisor data into the VM. The data involved may be limited, or may
|
| /linux/Documentation/bpf/ |
| H A D | map_hash.rst | 233 other CPUs involved in the following operation attempts:
259 the top right provides indicators for which locks may be involved in specific
|