Home
last modified time | relevance | path

Searched refs:claiming (Results 1 – 8 of 8) sorted by relevance

/Linux-v5.10/fs/
Dblock_dev.c1446 struct block_device *whole = NULL, *claiming = NULL; in __blkdev_get() local
1470 claiming = whole; in __blkdev_get()
1472 claiming = bdev; in __blkdev_get()
1473 ret = bd_prepare_to_claim(bdev, claiming, holder); in __blkdev_get()
1554 if (claiming) in __blkdev_get()
1555 bd_finish_claiming(bdev, claiming, holder); in __blkdev_get()
1563 if (claiming && (mode & FMODE_WRITE) && !bdev->bd_write_holder && in __blkdev_get()
1588 if (claiming) in __blkdev_get()
1589 bd_abort_claiming(bdev, claiming, holder); in __blkdev_get()
/Linux-v5.10/Documentation/hwmon/
Dabituguru.rst96 W83L950D in disguise (despite Abit claiming it is "a new microprocessor
/Linux-v5.10/arch/arm64/boot/dts/amlogic/
Dmeson-gxl-s805x-libretech-ac.dts83 * claiming it as done below reset the board anyway
/Linux-v5.10/Documentation/pcmcia/
Ddriver-changes.rst146 authors are now responsible for claiming your resources as per
/Linux-v5.10/Documentation/driver-api/media/
Dcec-core.rst405 claiming the logical addresses. If block is true, then this function won't
/Linux-v5.10/Documentation/vm/
Dfrontswap.rst144 request (i.e. provides no memory despite claiming it might),
/Linux-v5.10/Documentation/driver-api/usb/
Dusb.rst338 endpoints, reading or writing data and claiming exclusive use of an
496 This includes claiming arbitrary interfaces, resetting a device on
/Linux-v5.10/Documentation/driver-api/
Dparport-lowlevel.rst74 claiming a port for exclusive use, and so on. They also include