Home
last modified time | relevance | path

Searched full:involved (Results 1 – 25 of 549) sorted by relevance

12345678910>>...22

/OK3568_Linux_fs/kernel/Documentation/process/
H A Dembargoed-hardware-issues.rst103 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:
H A Dcode-of-conduct-interpretation.rst18 kernel. Know that this happens because everyone involved wants to see
63 and the technical complexity involved naturally require expertise and
H A D2.Process.rst7 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
151 kernel. There is, instead, a somewhat involved (if somewhat informal)
214 involved.
434 the Cc: header for all involved. In the absence of a strong reason (such
H A Dadding-syscalls.rst7 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
/OK3568_Linux_fs/kernel/arch/um/
H A DKconfig.debug13 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,
/OK3568_Linux_fs/yocto/poky/meta/files/common-licenses/
H A DArtistic-1.013 …justify on the basis of media cost, duplication charges, time of people involved, and so on. (You …
14 …ns that no fee is charged for the item itself, though there may be fees involved in handling the i…
H A DOGTSL54 involved, and so on. (You will not be required to justify it
58 itself, though there may be fees involved in handling the
H A DNBPL-1.021 …justify on the basis of media cost, duplication charges, time of people involved, and so on. (You …
23 …ns that no fee is charged for the item itself, though there may be fees involved in handling the i…
H A DOLDAP-1.222 …justify on the basis of media cost, duplication charges, time of people involved, and so on. (You …
24 …ns that no fee is charged for the item itself, though there may be fees involved in handling the i…
H A DArtistic-1.0-cl817 …justify on the basis of media cost, duplication charges, time of people involved, and so on. (You …
19 …ns that no fee is charged for the item itself, though there may be fees involved in handling the i…
H A DOLDAP-1.122 …justify on the basis of media cost, duplication charges, time of people involved, and so on. (You …
24 …ns that no fee is charged for the item itself, though there may be fees involved in handling the i…
H A DOLDAP-1.322 …justify on the basis of media cost, duplication charges, time of people involved, and so on. (You …
24 …ns that no fee is charged for the item itself, though there may be fees involved in handling the i…
H A DArtistic-1.0-Perl17 …justify on the basis of media cost, duplication charges, time of people involved, and so on. (You…
19 …ns that no fee is charged for the item itself, though there may be fees involved in handling the i…
H A DOLDAP-1.422 …justify on the basis of media cost, duplication charges, time of people involved, and so on. (You …
24 …ns that no fee is charged for the item itself, though there may be fees involved in handling the i…
/OK3568_Linux_fs/kernel/Documentation/power/
H A Dsuspend-and-cpuhotplug.rst18 the locking involved. It outlines the notifications involved as well.
173 II. What are the issues involved in CPU hotplug?
/OK3568_Linux_fs/kernel/sound/soc/sof/
H A DKconfig61 Say Y if you are involved in SOF development and need this option
96 If you are not involved in SOF releases and CI development
/OK3568_Linux_fs/u-boot/drivers/video/
H A DKconfig356 This is one of the SPI communication pins, involved in setting up a
366 This is one of the SPI communication pins, involved in setting up a
376 This is one of the SPI communication pins, involved in setting up a
386 This is one of the SPI communication pins, involved in setting up a
/OK3568_Linux_fs/kernel/Documentation/driver-api/pci/
H A Dp2pdma.rst17 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
/OK3568_Linux_fs/buildroot/package/dieharder/
H A DConfig.in5 dieharder is a fairly involved random number/uniform deviate
/OK3568_Linux_fs/u-boot/tools/binman/etype/
H A Du_boot_spl_with_ucode_ptr.py20 See Entry_u_boot_ucode for full details of the entries involved in this
/OK3568_Linux_fs/u-boot/api/
H A Dapi_platform-mips.c23 * need to reflect their current state and layout of structures involved!
/OK3568_Linux_fs/kernel/arch/arm/mach-mmp/
H A Dplatsmp.c17 * there. No IPIs involved. in mmp3_boot_secondary()
/OK3568_Linux_fs/buildroot/package/nginx-naxsi/
H A DConfig.in12 containing 99% of known patterns involved in website
/OK3568_Linux_fs/kernel/include/linux/mmc/
H A Dpm.h16 * abstractions involved, from the host controller driver, to the MMC core
/OK3568_Linux_fs/kernel/Documentation/core-api/irq/
H A Dconcepts.rst23 of the hardware involved. The ISA IRQs are a classic example of

12345678910>>...22