Searched full:involved (Results 1 – 25 of 364) sorted by relevance
12345678910>>...15
| /Linux-v6.1/Documentation/process/ |
| 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
143 response team, but is not necessarily involved in the mitigation
216 The involved parties will negotiate the date and time where the embargo
222 required for all involved parties to develop, test and prepare the
225 the involved developers and response teams as the patches need to be kept
242 reporting process and further handling. Ambassadors are not involved in the
244 an involved disclosed party. The current ambassadors list:
|
| 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
|
| 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
|
| 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
|
| 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
372 If there's a pointer-to-a-pointer involved, the decision is easy: x32 is
381 If no pointers are involved, then it is preferable to re-use the 64-bit system
385 In either case, you should check that the types involved in your argument
|
| 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.
|
| D | 8.Conclusion.rst | 72 everybody involved wins. Fire up your editor and come join us; you will be
|
| /Linux-v6.1/arch/um/ |
| 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-v6.1/sound/soc/sof/ |
| 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,
|
| /Linux-v6.1/Documentation/power/ |
| 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-v6.1/include/linux/mmc/ |
| D | pm.h | 16 * abstractions involved, from the host controller driver, to the MMC core
|
| /Linux-v6.1/arch/arm/mach-mmp/ |
| D | platsmp.c | 17 * there. No IPIs involved. in mmp3_boot_secondary()
|
| /Linux-v6.1/Documentation/gpu/rfc/ |
| D | index.rst | 11 mailing lists and involved people outside of dri-devel.
|
| /Linux-v6.1/Documentation/driver-api/pci/ |
| D | p2pdma.rst | 17 only supports doing P2P when the endpoints involved are all behind the
105 all client devices that will be involved in a given transaction. For
|
| /Linux-v6.1/Documentation/core-api/irq/ |
| D | concepts.rst | 23 of the hardware involved. The ISA IRQs are a classic example of
|
| /Linux-v6.1/Documentation/filesystems/ext4/ |
| D | super.rst | 367 - inode involved in first error.
371 - Number of block involved of first error.
387 - inode involved in most recent error.
395 - Number of block involved in most recent error.
|
| /Linux-v6.1/Documentation/loongarch/ |
| D | booting.rst | 25 All pointers involved at this stage are in physical addresses.
|
| /Linux-v6.1/arch/arm/include/asm/ |
| D | highmem.h | 30 * the locking involved must also disable IRQs which is incompatible with
|
| /Linux-v6.1/arch/mips/include/asm/dec/ |
| D | ecc.h | 23 #define KN0X_EAR_ADDRESS (0x7ffffff<<0) /* address involved */
|
| /Linux-v6.1/Documentation/mhi/ |
| D | topology.rst | 16 It is however not involved in the actual data transfer as the data transfer
|
| /Linux-v6.1/tools/perf/Documentation/ |
| D | Build.txt | 48 NOTE this description is omitting other libraries involved, only
|
| /Linux-v6.1/Documentation/s390/ |
| D | qeth.rst | 44 if no VLAN is involved in the event.
|
| /Linux-v6.1/drivers/s390/scsi/ |
| D | zfcp_dbf.c | 231 * @pl: array of all involved sbals
288 * @port: remote port involved in the erp_action
289 * @sdev: scsi device involved in the erp_action
334 * @port: remote port involved in the erp_action
335 * @sdev: scsi device involved in the erp_action
|
| /Linux-v6.1/Documentation/arm/samsung/ |
| D | overview.rst | 66 where to simplify the include and dependency issues involved with having
|
| /Linux-v6.1/Documentation/powerpc/ |
| D | cpu_features.rst | 27 Implementing cpufeatures in assembly is a little more involved. There are
|
12345678910>>...15
