Home
last modified time | relevance | path

Searched refs:relevant (Results 1 – 25 of 301) sorted by relevance

12345678910>>...13

/linux-6.12.1/tools/power/cpupower/debug/i386/
Ddump_psb.c22 static long relevant; variable
112 if (relevant != 0) { in decode_psb()
113 if (relevant!= pst->cpuid) in decode_psb()
164 relevant = strtol(optarg, NULL, 16); in main()
/linux-6.12.1/scripts/coccinelle/api/
Dmemdup_user.cocci22 def relevant(p):
28 position p : script:python() { relevant(p) };
53 position p : script:python() { relevant(p) };
75 position p : script:python() { relevant(p) };
88 position p : script:python() { relevant(p) };
Dkfree_sensitive.cocci24 def relevant(p):
36 position p : script:python() { relevant(p) };
52 position p : script:python() { relevant(p) };
70 position p : script:python() { relevant(p) };
Dkvmalloc.cocci20 def relevant(p):
72 position p : script:python() { relevant(p) };
225 position p : script:python() { relevant(p) };
/linux-6.12.1/scripts/coccinelle/misc/
Dflexible_array.cocci20 def relevant(positions):
29 position p : script:python() { relevant(p) };
73 position p : script:python() { relevant(p) };
/linux-6.12.1/Documentation/virt/kvm/devices/
Dmpic.rst31 to the relevant MSIIR.
42 byte offset of the relevant IVPR from EIVPR0, divided by 32.
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dvidioc-enum-fmt.rst198 colorspace. This flag is relevant only for capture devices.
205 transfer function. This flag is relevant only for capture devices.
212 Y'CbCr encoding. This flag is relevant only for capture devices.
219 HSV encoding. This flag is relevant only for capture devices.
226 quantization. This flag is relevant only for capture devices.
/linux-6.12.1/net/can/j1939/
DKconfig13 The relevant parts in kernel are
/linux-6.12.1/Documentation/gpu/amdgpu/display/
Ddc-debug.rst84 an issue arises is some generic timeout error. So, to get more relevant
85 information, we can trace DMUB commands by enabling the relevant bits in
116 enabling the relevant bits in the mask before reproducing the issue and
/linux-6.12.1/Documentation/process/
Dcve.rst70 change lies solely with the maintainers of the relevant subsystem
107 large numbers of assigned CVEs are not relevant for their systems.
111 specific CVE is relevant for your system.
120 might be relevant to take.
/linux-6.12.1/drivers/misc/ti-st/
DKconfig16 are returned to relevant protocol drivers based on their
/linux-6.12.1/Documentation/tools/rtla/
Dcommon_timerlat_description.rst9 handler. It also enable the trace of the most relevant information via
/linux-6.12.1/Documentation/firmware-guide/acpi/dsd/
Dleds.rst25 referring to the "reg" property of the relevant LED, is used to identify
38 show below. Objects not relevant for LEDs or the references to them have been
/linux-6.12.1/Documentation/gpu/rfc/
Dindex.rst10 considerations. Especially for uapi make sure you Cc: all relevant project
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-devices-waiting_for_supplier9 information is no longer relevant). The number read from it (0
Dsysfs-class-net-statistics7 This value might not be relevant with all MAC layers.
32 network device. This value might only be relevant for interfaces
161 this might only be relevant for devices that support
Dppc-memtrace5 Description: This folder contains the relevant debugfs files for the
/linux-6.12.1/drivers/staging/rtl8192e/
DTODO12 * Remove the HAL layer and migrate its functionality into the relevant parts of
/linux-6.12.1/Documentation/arch/arc/
Darc.rst10 ARC processors and relevant open source projects.
13 Good place to start to find relevant FOSS projects, toolchain releases,
/linux-6.12.1/Documentation/devicetree/bindings/i2c/
Di2c-opal.txt13 the relevant OPAL functions.
/linux-6.12.1/arch/alpha/lib/
Dev6-memset.S87 mskql $4,$16,$4 # U : clear relevant parts of the quad
265 mskql $4,$16,$4 # U : clear relevant parts of the quad
453 mskql $4,$16,$4 # U : clear relevant parts of the quad
/linux-6.12.1/Documentation/usb/
Dohci.rst32 work on while the OS is getting around to the relevant IRQ processing.
/linux-6.12.1/usr/
DKconfig118 decompression speed. Compression speed is only relevant
119 when building a kernel. Decompression speed is relevant at
121 relevant on memory constrained systems. This is usually based on the
/linux-6.12.1/Documentation/scsi/
D53c700.rst79 the relevant request_*_region function and place the register base
93 where host is the return from the relevant NCR_700_detect() routine.
/linux-6.12.1/drivers/staging/vc04_services/interface/
DTODO27 indentation deep making it very unpleasant to read. This is specially relevant

12345678910>>...13