Home
last modified time | relevance | path

Searched full:unavoidable (Results 1 – 25 of 38) sorted by relevance

12

/linux-6.12.1/Documentation/devicetree/bindings/watchdog/
Drealtek,otto-wdt.yaml21 unavoidable, unless the WDT is disabled.
/linux-6.12.1/arch/arm64/kernel/pi/
Drelacheck.c95 * initialized absolute symbol references are unavoidable, they in main()
/linux-6.12.1/tools/testing/selftests/x86/
DMakefile46 # linking stage, so a compiler warning is unavoidable without (wastefully)
/linux-6.12.1/Documentation/locking/
Dpi-futex.rst52 unavoidable fact of life, and once we accept that multi-task userspace
/linux-6.12.1/drivers/iio/accel/
Dbmc150-accel-i2c.c73 * This is unavoidable since the _DSM implementation expects a "naked" in bmc150_acpi_set_angle_dsm()
/linux-6.12.1/include/asm-generic/
Ddiv64.h128 * If ___bits == 0 then setting bit 31 is unavoidable. \
/linux-6.12.1/drivers/dax/
Dkmem.c83 * unavoidable performance issues. in dev_dax_kmem_probe()
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dvidioc-querycap.rst60 unavoidable here. Drivers and applications should take precautions
/linux-6.12.1/fs/ecryptfs/
Dfile.c106 * encryption being enabled. One unavoidable example would be in ecryptfs_filldir()
/linux-6.12.1/lib/
Ddhry.h120 * degree, this is unavoidable for small synthetic benchmarks.
/linux-6.12.1/fs/vboxsf/
Dutils.c226 * this is unavoidable. in vboxsf_inode_revalidate()
/linux-6.12.1/drivers/scsi/
Dmac_scsi.c103 * so bus errors are unavoidable.
/linux-6.12.1/Documentation/target/
Dtcmu-design.rst79 potentially to malfunction. This is unavoidable, but hopefully not
/linux-6.12.1/drivers/hwmon/
Dnzxt-smart2.c365 * fancontrol to shut down. So the wait is unavoidable. in nzxt_smart2_hwmon_read()
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-class-power631 is needed for unavoidable corrections of aging batteries.
/linux-6.12.1/drivers/comedi/drivers/
Djr3_pci.h577 * is probably unavoidable in these environments. On the occasions
/linux-6.12.1/Documentation/driver-api/gpio/
Ddriver.rst73 a GPIO controller should be rare; use gpiochip_remove() when it is unavoidable.
/linux-6.12.1/kernel/futex/
Dcore.c300 * folio lock will be acquired only if it is unavoidable in get_futex_key()
/linux-6.12.1/arch/arm64/kvm/
Darch_timer.c535 * Do it unconditionally, as this is either unavoidable in timer_save_state()
/linux-6.12.1/drivers/ata/
Dsata_sil24.c1105 * unavoidable and much better than losing interrupts which in sil24_host_intr()
/linux-6.12.1/Documentation/process/
Dhandling-regressions.rst502 that were basically entirely unavoidable, and people _tried_hard_ to
/linux-6.12.1/fs/overlayfs/
Dinode.c230 * additional vfs_getattr() is unavoidable. in ovl_getattr()
/linux-6.12.1/Documentation/driver-api/
Dpin-control.rst1283 themselves, but again sometimes this is unavoidable.
/linux-6.12.1/drivers/usb/gadget/function/
Df_mass_storage.c144 * too much data, implementing this would cause an unavoidable race.
2202 * (6.6.1), so it's unavoidable. It also says we must in received_cbw()
/linux-6.12.1/tools/testing/selftests/mm/
Dpagemap_ioctl.c1449 * unavoidable as soft dirty flag is handled in software through page faults in transact_test()

12