Searched full:concerns (Results 1 – 25 of 67) sorted by relevance
123
/linux-6.12.1/drivers/pci/hotplug/ |
D | TODO | 18 * A large portion of cpqphp_ctrl.c and cpqphp_pci.c concerns resource 47 * A large portion of ibmphp_res.c and ibmphp_pci.c concerns resource
|
/linux-6.12.1/Documentation/scsi/ |
D | sym53c500_cs.rst | 9 long overdue, and the current version addresses the following concerns:
|
/linux-6.12.1/Documentation/gpu/ |
D | panfrost.rst | 43 because of power saving concerns. `fdinfo` users and benchmark applications which
|
/linux-6.12.1/Documentation/devicetree/bindings/display/ |
D | dsi-controller.yaml | 22 Notice: this binding concerns DSI panels connected directly to a master
|
/linux-6.12.1/drivers/gpu/drm/nouveau/nvkm/subdev/pci/ |
D | g84.c | 105 /* The following only concerns PCIe cards. */ in g84_pci_init()
|
/linux-6.12.1/arch/arm64/hyperv/ |
D | hv_core.c | 140 * concerns about the more verbose version.
|
/linux-6.12.1/Documentation/security/ |
D | lsm.rst | 131 based on overhead, complexity and performance concerns.
|
/linux-6.12.1/Documentation/process/ |
D | code-of-conduct-interpretation.rst | 45 documents final escalation paths in case of unresolved concerns
|
/linux-6.12.1/Documentation/filesystems/ext4/ |
D | blockgroup.rst | 83 Without the option META_BG, for safety concerns, all block group
|
/linux-6.12.1/security/ |
D | Kconfig | 132 Intel TXT also helps solve real end user concerns about having
|
/linux-6.12.1/tools/testing/selftests/rseq/ |
D | basic_percpu_ops_test.c | 198 * rseq primitive allows us to implement pop without concerns over
|
/linux-6.12.1/drivers/staging/media/atomisp/pci/isp/kernels/dvs/dvs_1.0/ |
D | ia_css_dvs.host.c | 84 …o_width)); // round num_x up to blockdim_x, if it concerns the Y0Y1 block (uv_flag==0) round up to… in convert_coords_to_ispparams()
|
/linux-6.12.1/Documentation/driver-api/media/drivers/ |
D | ipu6.rst | 63 To address the IPU6 firmware security concerns, the IPU6 firmware needs to
|
/linux-6.12.1/Documentation/devicetree/bindings/mfd/ |
D | stericsson,ab8500.yaml | 450 concerns the autonomous regulators VSMPS1, VSMPS2 and VSMPS3
|
/linux-6.12.1/Documentation/arch/powerpc/ |
D | hvcs.rst | 417 Q: What are the security concerns involving hvcs? 419 A: There are three main security concerns:
|
/linux-6.12.1/arch/s390/pci/ |
D | pci_event.c | 283 case 0x002a: /* Error event concerns FMB */ in __zpci_event_error()
|
/linux-6.12.1/Documentation/core-api/ |
D | this_cpu_ops.rst | 311 One example that illustrates some concerns with write operations is
|
/linux-6.12.1/LICENSES/deprecated/ |
D | GPL-1.0 | 162 address new problems or concerns.
|
/linux-6.12.1/arch/sparc/kernel/ |
D | wof.S | 317 /* Because of SMP concerns and speed we play a trick.
|
/linux-6.12.1/tools/memory-model/Documentation/ |
D | simple.txt | 74 Even if performance and scalability concerns prevent your code from
|
/linux-6.12.1/drivers/base/ |
D | auxiliary.c | 30 * compartmentalize, layer, and distribute domain-specific concerns via a Linux
|
/linux-6.12.1/drivers/media/platform/ti/cal/ |
D | cal_regs.h | 22 * | 0x4845 B384 [28:27] = 0x2) mode. Common concerns include: high
|
/linux-6.12.1/include/uapi/linux/ |
D | dm-log-userspace.h | 378 * set to zero and are reserved for future use and compatibility concerns.
|
/linux-6.12.1/drivers/gpu/drm/i915/gt/ |
D | intel_breadcrumbs.c | 195 * interrupts are always enabled due to concerns with rc6 being in signal_irq_work()
|
/linux-6.12.1/drivers/gpu/drm/i915/gvt/ |
D | vgpu.c | 418 * is required both for functionary and security concerns.The ultimate goal
|
123