Searched refs:surprise (Results 1 – 14 of 14) sorted by relevance
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/poppler/ |
H A D | poppler_25.01.0.bb | 29 # surprise - did not expect this to work :)
|
/openbmc/linux/block/ |
H A D | bdev.c | 1009 void bdev_mark_dead(struct block_device *bdev, bool surprise) in bdev_mark_dead() argument 1013 bdev->bd_holder_ops->mark_dead(bdev, surprise); in bdev_mark_dead()
|
H A D | genhd.c | 557 static void blk_report_disk_dead(struct gendisk *disk, bool surprise) in blk_report_disk_dead() argument 568 bdev_mark_dead(bdev, surprise); in blk_report_disk_dead()
|
/openbmc/linux/Documentation/filesystems/ |
H A D | inotify.rst | 61 example, love it. Trust me, I asked. It is not a surprise: Who'd want
|
/openbmc/linux/include/linux/ |
H A D | blkdev.h | 768 void bdev_mark_dead(struct block_device *bdev, bool surprise); 1478 void (*mark_dead)(struct block_device *bdev, bool surprise);
|
/openbmc/linux/fs/ |
H A D | super.c | 1451 static void fs_bdev_mark_dead(struct block_device *bdev, bool surprise) in fs_bdev_mark_dead() argument 1461 if (!surprise) in fs_bdev_mark_dead()
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | locking.txt | 113 no surprise that "r2" can be zero, and a quick herd7 run confirms this.
|
/openbmc/linux/Documentation/admin-guide/mm/ |
H A D | concepts.rst | 179 repurposing them is called (surprise!) `reclaim`. Linux can reclaim
|
/openbmc/linux/Documentation/RCU/ |
H A D | rcubarrier.rst | 343 in later surprise bugs when the implementation changes.
|
/openbmc/qemu/docs/specs/ |
H A D | ppc-spapr-numa.rst | 235 avoid being taken by surprise with that the guest is actually seeing in the
|
/openbmc/linux/Documentation/RCU/Design/Requirements/ |
H A D | Requirements.rst | 1116 It often comes as a surprise that many algorithms do not require a 1977 accumulation by these kthreads. This requirement was no surprise, but 1979 built with ``CONFIG_NO_HZ_FULL=y`` `did come as a surprise 2007 needed fix, so this surprise requirement was relatively painless. 2305 surprise, the sub-100-microsecond real-time latency budget `applies to 2324 Although the need for ``rcutorture`` was no surprise, the current
|
/openbmc/linux/Documentation/scsi/ |
H A D | st.rst | 274 cause a surprise when moving from 2.4. There small writes (e.g., tar without
|
/openbmc/openbmc/poky/documentation/contributor-guide/ |
H A D | submit-changes.rst | 28 often the surprise reviewer that catches the most interesting issues!
|
/openbmc/linux/Documentation/ |
H A D | memory-barriers.txt | 1666 surprise if some other CPU might have stored to variable 'a' in the
|