Home
last modified time | relevance | path

Searched full:deserves (Results 1 – 25 of 45) sorted by relevance

12

/kernel/linux/linux-5.10/drivers/staging/comedi/drivers/
Dcb_pcimdda.c53 * deserves its own driver file.
/kernel/linux/linux-6.6/drivers/comedi/drivers/
Dcb_pcimdda.c53 * deserves its own driver file.
/kernel/linux/linux-5.10/Documentation/process/
Dstable-kernel-rules.rst83 it deserves more regression testing first). :ref:`option_3` is especially
/kernel/linux/linux-6.6/arch/sparc/kernel/
Dsyscalls.S82 * XXX upon the Y register being preserved across a fork deserves
/kernel/linux/linux-6.6/Documentation/admin-guide/mm/
Dconcepts.rst9 definitely deserves a dedicated document, which hopefully will be
/kernel/linux/linux-5.10/arch/sparc/kernel/
Dsyscalls.S82 * XXX upon the Y register being preserved across a fork deserves
/kernel/linux/linux-6.6/Documentation/gpu/amdgpu/display/
Ddcn-overview.rst73 the Global Sync deserves an extra level of detail described in the next
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/cable/
Dsb1000.rst13 This driver was written by Franco Venturi <fventuri@mediaone.net>. He deserves
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
Dconcepts.rst11 definitely deserves a dedicated document, which hopefully will be
/kernel/linux/linux-6.6/Documentation/networking/device_drivers/cable/
Dsb1000.rst13 This driver was written by Franco Venturi <fventuri@mediaone.net>. He deserves
/kernel/linux/linux-5.10/Documentation/driver-api/usb/
Dtypec.rst69 deserves special notice. If the port that is being registered does not have
/kernel/linux/linux-6.6/Documentation/driver-api/usb/
Dtypec.rst69 deserves special notice. If the port that is being registered does not have
/kernel/linux/linux-6.6/lib/
Dklist.c61 /* no knode deserves to start its life dead */ in knode_set_klist()
/kernel/linux/linux-5.10/lib/
Dklist.c61 /* no knode deserves to start its life dead */ in knode_set_klist()
/kernel/linux/linux-5.10/drivers/net/hamradio/
Dbpqether.c20 * - it just deserves to "live" as an own driver
/kernel/linux/linux-6.6/Documentation/networking/
Dnexthop-group-resilient.rst79 In a nutshell, the algorithm works as follows. Each next hop deserves a
/kernel/linux/linux-6.6/drivers/net/hamradio/
Dbpqether.c20 * - it just deserves to "live" as an own driver
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Didle-states.yaml123 The min-residency time parameter deserves further explanation since it is
/kernel/linux/linux-6.6/Documentation/userspace-api/netlink/
Dintro.rst547 Real documentation of that family, deserves a chapter (or a book) of its own.
/kernel/linux/linux-5.10/drivers/dma-buf/
Ddma-fence.c226 * * &struct dma_resv deserves a special note, since the readers are only
/kernel/linux/linux-5.10/arch/arm64/kvm/vgic/
Dvgic.c994 * We've injected an interrupt, time to find out who deserves in vgic_kick_vcpus()
/kernel/linux/linux-5.10/fs/ntfs/
Ddir.c692 * anyone doing screwy stuff like that deserves to burn in
879 * anyone doing screwy stuff like that deserves to burn in
/kernel/linux/linux-6.6/fs/ntfs/
Ddir.c692 * anyone doing screwy stuff like that deserves to burn in
879 * anyone doing screwy stuff like that deserves to burn in
/kernel/linux/linux-6.6/arch/arm64/kvm/vgic/
Dvgic.c1013 * We've injected an interrupt, time to find out who deserves in vgic_kick_vcpus()
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/cpu/
Didle-states.yaml143 The min-residency time parameter deserves further explanation since it is

12