Searched full:unavoidable (Results 1 – 25 of 38) sorted by relevance
12
/linux-6.12.1/Documentation/devicetree/bindings/watchdog/ |
D | realtek,otto-wdt.yaml | 21 unavoidable, unless the WDT is disabled.
|
/linux-6.12.1/arch/arm64/kernel/pi/ |
D | relacheck.c | 95 * initialized absolute symbol references are unavoidable, they in main()
|
/linux-6.12.1/tools/testing/selftests/x86/ |
D | Makefile | 46 # linking stage, so a compiler warning is unavoidable without (wastefully)
|
/linux-6.12.1/Documentation/locking/ |
D | pi-futex.rst | 52 unavoidable fact of life, and once we accept that multi-task userspace
|
/linux-6.12.1/drivers/iio/accel/ |
D | bmc150-accel-i2c.c | 73 * This is unavoidable since the _DSM implementation expects a "naked" in bmc150_acpi_set_angle_dsm()
|
/linux-6.12.1/include/asm-generic/ |
D | div64.h | 128 * If ___bits == 0 then setting bit 31 is unavoidable. \
|
/linux-6.12.1/drivers/dax/ |
D | kmem.c | 83 * unavoidable performance issues. in dev_dax_kmem_probe()
|
/linux-6.12.1/Documentation/userspace-api/media/v4l/ |
D | vidioc-querycap.rst | 60 unavoidable here. Drivers and applications should take precautions
|
/linux-6.12.1/fs/ecryptfs/ |
D | file.c | 106 * encryption being enabled. One unavoidable example would be in ecryptfs_filldir()
|
/linux-6.12.1/lib/ |
D | dhry.h | 120 * degree, this is unavoidable for small synthetic benchmarks.
|
/linux-6.12.1/fs/vboxsf/ |
D | utils.c | 226 * this is unavoidable. in vboxsf_inode_revalidate()
|
/linux-6.12.1/drivers/scsi/ |
D | mac_scsi.c | 103 * so bus errors are unavoidable.
|
/linux-6.12.1/Documentation/target/ |
D | tcmu-design.rst | 79 potentially to malfunction. This is unavoidable, but hopefully not
|
/linux-6.12.1/drivers/hwmon/ |
D | nzxt-smart2.c | 365 * fancontrol to shut down. So the wait is unavoidable. in nzxt_smart2_hwmon_read()
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-class-power | 631 is needed for unavoidable corrections of aging batteries.
|
/linux-6.12.1/drivers/comedi/drivers/ |
D | jr3_pci.h | 577 * is probably unavoidable in these environments. On the occasions
|
/linux-6.12.1/Documentation/driver-api/gpio/ |
D | driver.rst | 73 a GPIO controller should be rare; use gpiochip_remove() when it is unavoidable.
|
/linux-6.12.1/kernel/futex/ |
D | core.c | 300 * folio lock will be acquired only if it is unavoidable in get_futex_key()
|
/linux-6.12.1/arch/arm64/kvm/ |
D | arch_timer.c | 535 * Do it unconditionally, as this is either unavoidable in timer_save_state()
|
/linux-6.12.1/drivers/ata/ |
D | sata_sil24.c | 1105 * unavoidable and much better than losing interrupts which in sil24_host_intr()
|
/linux-6.12.1/Documentation/process/ |
D | handling-regressions.rst | 502 that were basically entirely unavoidable, and people _tried_hard_ to
|
/linux-6.12.1/fs/overlayfs/ |
D | inode.c | 230 * additional vfs_getattr() is unavoidable. in ovl_getattr()
|
/linux-6.12.1/Documentation/driver-api/ |
D | pin-control.rst | 1283 themselves, but again sometimes this is unavoidable.
|
/linux-6.12.1/drivers/usb/gadget/function/ |
D | f_mass_storage.c | 144 * 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/ |
D | pagemap_ioctl.c | 1449 * unavoidable as soft dirty flag is handled in software through page faults in transact_test()
|
12