Home
last modified time | relevance | path

Searched full:understood (Results 1 – 25 of 131) sorted by relevance

123456

/Linux-v6.6/rust/
Dbindgen_parameters21 # `seccomp`'s comment gets understood as a doctest
/Linux-v6.6/security/smack/
DKconfig29 access rule set once the behavior is well understood.
/Linux-v6.6/drivers/gpu/drm/nouveau/nvkm/subdev/therm/
Dgf100.c56 * TODO: Fermi clockgating isn't understood fully yet, so we don't specify any
/Linux-v6.6/Documentation/block/
Ddata-integrity.rst93 format that can be understood by the disk.
238 understood by the target device with the notable exception that
/Linux-v6.6/drivers/soc/sunxi/
Dsunxi_mbus.c82 * Older DTs or SoCs who are not clearly understood need to set in sunxi_mbus_notifier()
/Linux-v6.6/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/
Dnv50.c36 * 0x01/0x02 are values understood by the VRAM allocator, in nv50_mmu_kind()
/Linux-v6.6/drivers/spi/
Dspi-fsl-lib.c90 /* the spi->mode bits understood by this driver: */ in mpc8xxx_spi_probe()
/Linux-v6.6/Documentation/devicetree/bindings/hwmon/
Dntc-thermistor.yaml48 called "connected ground" and "connected positive" and shall be understood as
/Linux-v6.6/net/dccp/
Dfeat.h30 FEAT_UNKNOWN = 0xFF /* not understood or invalid feature */
/Linux-v6.6/include/uapi/linux/
Diommufd.h27 * understood, however a known field has a value the kernel does not
29 * - EINVAL: Everything about the IOCTL was understood, but a field is not
/Linux-v6.6/drivers/media/radio/
Dradio-terratec.c92 rest = freq * 10 + 10700; /* I once had understood what is going on here */ in terratec_s_frequency()
/Linux-v6.6/fs/ocfs2/
Docfs2_ioctl.h181 #define OCFS2_INFO_FL_FILLED (0x40000000) /* Filesystem understood
/Linux-v6.6/Documentation/security/
Dself-protection.rst147 understood is that of the stack buffer overflow in which the return
164 A less well understood attack is using a bug that triggers the
/Linux-v6.6/drivers/staging/vc04_services/vchiq-mmal/
Dmmal-encodings.h61 /** SAND Video (YUVUV128) format, native format understood by VideoCore.
/Linux-v6.6/drivers/staging/media/atomisp/i2c/
Datomisp-libmsrlisthelper.c59 * understood as an address in the sensor address space (hibyte in set_msr_configuration()
/Linux-v6.6/arch/arm/include/asm/
Decard.h20 * Currently understood cards (but not necessarily
/Linux-v6.6/Documentation/devicetree/bindings/bus/
Dqcom,ebi2.txt38 chip selects are understood fully. There is also a "byte device enable"
/Linux-v6.6/include/linux/
Dhte.h90 * @line_id: The logical ID understood by the consumers and providers.
/Linux-v6.6/fs/reiserfs/
DREADME110 curious, because he never really understood the value of our project,
/Linux-v6.6/arch/m68k/include/asm/
Dmac_psc.h25 * not understood as there seems to be only one input and one output buffer
/Linux-v6.6/drivers/pci/controller/
Dpci-hyperv.c2133 * @hbus: Root PCI bus, as understood by this driver
2197 * @hbus: Root PCI bus, as understood by this driver
2391 * @hbus: Root PCI bus, as understood by this driver
2522 * @hbus: Root PCI bus, as understood by this driver
2701 * @hbus: Root PCI bus, as understood by this driver
2746 * @hbus: Root PCI bus, as understood by this driver
2783 * @hbus: Root PCI bus, as understood by this driver
3177 * @hbus: Root PCI bus, as understood by this driver
3202 * @hbus: Root PCI bus, as understood by this driver
3280 * @hbus: Root PCI bus, as understood by this driver
/Linux-v6.6/Documentation/fb/
Dsisfb.rst135 off Disable sisfb. This option is only understood if sisfb is
/Linux-v6.6/Documentation/spi/
Dspidev.rst71 be understood by udev or mdev (udev replacement from BusyBox; it's less
/Linux-v6.6/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.rst218 Make sure you understood Documentation/process/submitting-patches.rst and send your patch to
/Linux-v6.6/Documentation/rust/
Dquick-start.rst108 the process can be tweaked using the environment variables understood by

123456