| /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 | 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/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/gpu/rfc/ |
| H A D | index.rst | 11 mailing lists and involved people outside of dri-devel.
|
| /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/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/arm/include/asm/ |
| H A D | highmem.h | 30 * the locking involved must also disable IRQs which is incompatible with
|
| /linux/arch/mips/include/asm/dec/ |
| H A D | ecc.h | 23 #define KN0X_EAR_ADDRESS (0x7ffffff<<0) /* address involved */
|
| /linux/drivers/s390/scsi/ |
| H A D | zfcp_dbf.c | 272 * @pl: array of all involved sbals
329 * @port: remote port involved in the erp_action
330 * @sdev: scsi device involved in the erp_action
375 * @port: remote port involved in the erp_action
376 * @sdev: scsi device involved in the erp_action
|
| /linux/Documentation/arch/s390/ |
| H A D | qeth.rst | 44 if no VLAN is involved in the event.
|
| /linux/arch/riscv/include/asm/ |
| H A D | pgtable-bits.h | 48 * Bit 4 is not involved into swap entry computation, so we
|
| /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
|
| /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/arch/powerpc/ |
| H A D | cpu_features.rst | 27 Implementing cpufeatures in assembly is a little more involved. There are
|
| /linux/security/selinux/ |
| H A D | xfrm.c | 418 /* This check even when there's no association involved is intended, in selinux_xfrm_sock_rcv_skb()
461 /* This check even when there's no association involved is intended, in selinux_xfrm_postroute_last()
|
| /linux/drivers/base/firmware_loader/builtin/ |
| H A D | main.c | 36 * is involved as these calls take place early in boot process. An example is
|
| /linux/include/soc/arc/ |
| H A D | mcip.h | 98 * - More involved commands setup MCIP_WDATA with cmd specific data
|