| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A D | arrayRCU.rst | 7 also be used to protect arrays. Three situations are as follows:
15 Each of these three situations involves an RCU-protected pointer to an
26 That aside, each of the three RCU-protected pointer situations are
37 to other array-of-list situations, such as radix trees.
|
| /OK3568_Linux_fs/kernel/Documentation/timers/ |
| H A D | no_hz.rst | 38 there are some situations where this old-school approach is still the
80 unnecessary scheduling-clock interrupts. In these situations, there
121 by one less than the number of CPUs. In these situations, there is
183 There are situations in which idle CPUs cannot be permitted to
265 of other situations where the scheduling-clock tick is not
282 Better handling of these sorts of situations is future work.
|
| /OK3568_Linux_fs/buildroot/package/patchelf/ |
| H A D | 0008-Use-sh_offset-instead-of-sh_addr-when-checking-alrea.patch | 9 This was not crashing in many situations because normally sh_address and
12 situations.
|
| /OK3568_Linux_fs/kernel/Documentation/locking/ |
| H A D | preempt-locking.rst | 15 requires explicit additional locking for very few additional situations.
18 requires protecting these situations.
35 protect these situations by disabling preemption around them.
|
| /OK3568_Linux_fs/kernel/arch/powerpc/include/asm/nohash/32/ |
| H A D | pte-44x.h | 60 * certain situations. In other words, in such situations some portion of
|
| /OK3568_Linux_fs/kernel/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 111 the mainline. The best practices to follow differ in those two situations.
190 as always, in such situations, the merge commit should explain why the
223 be situations that call out for a different solution, and these guidelines
|
| /OK3568_Linux_fs/kernel/Documentation/i2c/ |
| H A D | gpio-fault-injection.rst | 46 The following fault injectors create situations where SDA will be held low by a
47 device. Bus recovery should be able to fix these situations. But please note:
|
| /OK3568_Linux_fs/buildroot/package/iodine/ |
| H A D | Config.in | 6 This can be usable in different situations where
|
| /OK3568_Linux_fs/buildroot/package/earlyoom/ |
| H A D | Config.in | 8 before running out of memory, avoiding situations
|
| /OK3568_Linux_fs/buildroot/package/monit/ |
| H A D | Config.in | 10 actions in error situations.
|
| /OK3568_Linux_fs/kernel/Documentation/arm/ |
| H A D | vlocks.rst | 10 which are otherwise non-coherent, in situations where the hardware
89 vlocks are therefore best suited to situations where it is necessary
|
| /OK3568_Linux_fs/kernel/lib/zlib_inflate/ |
| H A D | Makefile | 13 # any nasty situations wrt memory management, and that the
|
| /OK3568_Linux_fs/buildroot/package/sqlcipher/ |
| H A D | Config.in | 28 plan under certain situations.
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/type_index/ |
| H A D | ctti_type_index.hpp | 18 /// It is used in situations when typeid() method is not available or
104 /// in situations when typeid() is working.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/p910nd/ |
| H A D | p910nd_0.97.bb | 1 DESCRIPTION = "A small network printer daemon for embedded situations that passes the job directly …
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/include/mbgl/util/ |
| H A D | ignore.hpp | 17 // std::initializer_list overload, for situations where you need sequenced
|
| /OK3568_Linux_fs/u-boot/doc/device-tree-bindings/net/ |
| H A D | fixed-link.txt | 5 normal MDIO-managed PHY device. For those situations, a Device Tree
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-devices-real_power_state | 17 In some situations the value of this attribute may be different
|
| H A D | sysfs-class-bdi | 46 situations where we want to avoid one device taking all or
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/regulator/ |
| H A D | qcom,usb-vbus-regulator.yaml | 14 regulator will be enabled in situations where the device is required to
|
| /OK3568_Linux_fs/buildroot/package/openal/ |
| H A D | Config.in | 8 # situations __atomic_*() or __sync_*() will be available, and not
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-kernel/linux/ |
| H A D | linux-dummy.bb | 3 provider for virtual/kernel to satisfy dependencies for situations \
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.displaying-bmps | 6 make sure all data is properly aligned, and in many situations simply choosing
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/ |
| H A D | drm_vblank_work.c | 25 * there's a few situations where it can't be helped. Some unforgiving
31 * context. Both of these situations can't be solved perfectly in Linux since
|
| /OK3568_Linux_fs/kernel/Documentation/power/ |
| H A D | pci.rst | 68 Thus in many situations both the native and the platform-based power management
231 may be identified later). The GPEs used in such situations are referred to as
302 These callbacks are executed by the PM core in various situations related to
407 situations. First, it may be called at the request of the device's driver, for
775 The freeze() callback is hibernation-specific and is executed in two situations,
920 The complete() callback is executed in the following situations:
1035 situations. If the PM core determines that the driver's "noirq" and "early"
1104 are a few situations in which power management requests are automatically
|