Searched refs:safely (Results 1 – 25 of 139) sorted by relevance
123456
| /Linux-v6.6/Documentation/hwmon/ |
| D | ltc4260.rst | 22 The LTC4260 Hot Swap controller allows a board to be safely inserted
30 which can be safely used to identify the chip. You will have to instantiate
|
| D | ltc4261.rst | 23 to be safely inserted and removed from a live backplane.
30 which can be safely used to identify the chip. You will have to instantiate
|
| D | ltc4151.rst | 29 which can be safely used to identify the chip. You will have to instantiate
|
| D | ltc4215.rst | 22 The LTC4215 controller allows a board to be safely inserted and removed
|
| D | lineage-pem.rst | 35 which can be safely used to identify the chip. You will have to instantiate
|
| D | ltc2945.rst | 30 which can be safely used to identify the chip. You will have to instantiate
|
| D | max16065.rst | 81 can be safely used to identify the chip. You will have to instantiate
|
| D | ltc4245.rst | 22 The LTC4245 controller allows a board to be safely inserted and removed
|
| /Linux-v6.6/net/batman-adv/ |
| D | Kconfig | 43 more than one mesh node in the same LAN, you can safely remove
54 this option you can safely remove it and save some space.
67 can safely disable it and save some space.
|
| /Linux-v6.6/drivers/net/ethernet/nxp/ |
| D | Kconfig | 9 some NXP LPC devices. You can safely enable this option for LPC32xx
|
| /Linux-v6.6/Documentation/RCU/ |
| D | rcuref.rst | 124 element can therefore safely be freed. This in turn guarantees that if
125 any reader finds the element, that reader may safely acquire a reference
|
| D | whatisRCU.rst | 107 to the data structure, so it now may safely be reclaimed
247 RCU-protected pointer, in order to safely communicate the change
269 then be safely dereferenced. Note that rcu_dereference()
752 to that data item, so we can safely reclaim it.
927 typically includes that spinlocks can still be safely locked, normal
928 reference counters can be safely manipulated, and ``__rcu`` pointers
929 can be safely dereferenced.
974 the individual objects and looks at how they can be accessed safely
|
| /Linux-v6.6/drivers/staging/media/av7110/ |
| D | video-command.rst | 66 This ensures it can be extended safely in the future. */
|
| /Linux-v6.6/drivers/net/ethernet/toshiba/ |
| D | Kconfig | 40 safely enable this option even if you have a wireless-less model.
|
| /Linux-v6.6/Documentation/watchdog/ |
| D | wdt.rst | 26 The ICS ISA-bus wdt card cannot be safely probed for. Instead you need to
|
| /Linux-v6.6/Documentation/i2c/ |
| D | old-module-parameters.rst | 8 safely skip this section.
|
| D | dma-considerations.rst | 25 flag with it. Then, the I2C core and drivers know they can safely operate DMA
|
| /Linux-v6.6/Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 7 controls safely.
324 safely.
337 enabled for the cluster. Other CPUs in the cluster can safely
355 enabled for the cluster. Other CPUs in the cluster can safely
460 be used to select a last man safely, before the CPUs become
|
| /Linux-v6.6/Documentation/driver-api/pldmfw/ |
| D | index.rst | 49 In order to safely process the firmware file, care is taken to avoid
|
| /Linux-v6.6/Documentation/process/ |
| D | magic-number.rst | 31 discipline, these cases get detected quickly and safely.
|
| /Linux-v6.6/Documentation/leds/ |
| D | leds-class-flash.rst | 79 This function can be safely called with NULL or error pointer argument.
|
| /Linux-v6.6/Documentation/arch/arm64/ |
| D | amu.rst | 52 The kernel can safely run a mix of CPUs with and without support for the
|
| /Linux-v6.6/Documentation/infiniband/ |
| D | core_locking.rst | 62 example, a consumer may safely call ib_poll_cq() on multiple CPUs
|
| /Linux-v6.6/Documentation/arch/ia64/ |
| D | aliasing.rst | 76 can referenced safely by an identity mapping.
167 region safely with kernel page table mappings, we can use
|
| /Linux-v6.6/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 94 | safely check the state from some other CPU. And even if it was |
95 | possible to safely check the state, it would still be necessary to |
96 | IPI the CPU to safely interact with the upcoming |
104 | and it would be able to safely detect that state without needing to |
173 clear can safely be ignored. However, it is possible for a CPU coming
|
123456
