/openbmc/linux/arch/arm/boot/dts/st/ |
H A D | ste-db9500.dtsi | 27 * be too careful, so reserve this memory anyway.
|
H A D | ste-db8520.dtsi | 45 * be too careful, so reserve this memory anyway.
|
H A D | ste-db8500.dtsi | 45 * be too careful, so reserve this memory anyway.
|
/openbmc/linux/Documentation/userspace-api/ |
H A D | no_new_privs.rst | 9 careful to prevent the parent from doing anything that could subvert the 36 Be careful, though: LSMs might also not tighten constraints on exec
|
/openbmc/linux/tools/power/cpupower/ |
H A D | TODO | 10 with a --force option and some "be careful" messages
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-core/images/ |
H A D | meta-networking-image-ptest.bb | 18 # The image can be sufficiently large (~1.8GB) that we need to be careful that it fits in a live
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/images/ |
H A D | meta-oe-image-ptest.bb | 18 # The image can be sufficiently large (~1.8GB) that we need to be careful that it fits in a live
|
/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/images/ |
H A D | meta-multimedia-image-ptest.bb | 18 # The image can be sufficiently large (~1.8GB) that we need to be careful that it fits in a live
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/images/ |
H A D | meta-filesystems-image-ptest.bb | 18 # The image can be sufficiently large (~1.8GB) that we need to be careful that it fits in a live
|
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-core/images/ |
H A D | meta-perl-image-ptest.bb | 18 # The image can be sufficiently large (~1.8GB) that we need to be careful that it fits in a live
|
/openbmc/openbmc/poky/meta/recipes-core/images/ |
H A D | core-image-ptest.bb | 17 # The image can sufficiently large (~1.8GB) that we need to be careful that it fits in a live
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-core/images/ |
H A D | meta-python-image-ptest.bb | 18 # The image can be sufficiently large (~1.8GB) that we need to be careful that it fits in a live
|
/openbmc/linux/Documentation/networking/ |
H A D | dctcp.rst | 20 but might need further careful tweaking.
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | tdx.rst | 114 careful to only reference shared pages it can safely handle a #VE. For 115 instance, the guest should be careful not to access shared memory in the 126 be careful not to access device MMIO regions unless it is also prepared to 164 However, the guest kernel must still be careful to avoid potential
|
H A D | pti.rst | 129 1. We can be more careful about not actually writing to CR3 178 careful and can be the cause of crashes that show up when
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/gperftools/gperftools/ |
H A D | 0001-src-mmap_hook.cc-Fix-build-for-32bit-machine.patch | 31 -// Linuxes with 32-bit off_t. We're being careful with mmap64 being
|
/openbmc/linux/Documentation/hwmon/ |
H A D | sht15.rst | 78 0 to disable it. Be careful not to enable the heater
|
H A D | smsc47m192.rst | 25 - Special thanks to Jean Delvare for careful checking
|
/openbmc/linux/Documentation/driver-api/pci/ |
H A D | p2pdma.rst | 27 be careful about what they do with them. 117 Driver writers should be very careful about not passing these special
|
/openbmc/qemu/docs/devel/migration/ |
H A D | virtio.rst | 107 Devices need to be careful in their state processing during load: The
|
/openbmc/u-boot/doc/device-tree-bindings/clock/ |
H A D | nvidia,tegra20-car.txt | 22 within the CLK_OUT_ENB or RST_DEVICES registers should be careful to
|
/openbmc/linux/fs/ubifs/ |
H A D | Kconfig | 61 so be careful. How often atime is updated depends on the selected strategy:
|
/openbmc/openbmc/poky/meta/classes-global/ |
H A D | devshell.bbclass | 32 # devshell and fakeroot/pseudo need careful handling since only the final
|
/openbmc/linux/Documentation/driver-api/tty/ |
H A D | tty_ldisc.rst | 79 calling its own functions must be careful in this case.
|
/openbmc/linux/Documentation/core-api/ |
H A D | gfp_mask-from-fs-io.rst | 13 Code paths in the filesystem and IO stacks must be careful when
|