| /linux/Documentation/hwmon/ |
| H A 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
|
| H A 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
|
| H A D | ltc4151.rst | 29 which can be safely used to identify the chip. You will have to instantiate
|
| H A D | ltc4215.rst | 22 The LTC4215 controller allows a board to be safely inserted and removed
|
| H A D | ltc4282.rst | 24 The LTC4282 hot swap controller allows a board to be safely inserted and removed
35 and power supplies must safely operate. Non-volatile configuration allows for
|
| H A D | lineage-pem.rst | 35 which can be safely used to identify the chip. You will have to instantiate
|
| H A D | ltc2945.rst | 30 which can be safely used to identify the chip. You will have to instantiate
|
| H A D | ltc4245.rst | 22 The LTC4245 controller allows a board to be safely inserted and removed
|
| H A D | max16065.rst | 81 can be safely used to identify the chip. You will have to instantiate
|
| /linux/drivers/net/ethernet/nxp/ |
| H A D | Kconfig | 9 some NXP LPC devices. You can safely enable this option for LPC32xx
|
| /linux/net/batman-adv/ |
| H A D | Kconfig | 44 more than one mesh node in the same LAN, you can safely remove
55 this option you can safely remove it and save some space.
|
| /linux/Documentation/RCU/ |
| H A 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
|
| /linux/drivers/net/ethernet/toshiba/ |
| H A D | Kconfig | 40 safely enable this option even if you have a wireless-less model.
|
| /linux/Documentation/core-api/real-time/ |
| H A D | architecture-porting.rst | 59 protected code to run safely in both thread and softirq contexts.
102 allows printk() to be safely used in atomic contexts.
|
| /linux/Documentation/arch/arm/ |
| H A 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/Documentation/watchdog/ |
| H A D | wdt.rst | 26 The ICS ISA-bus wdt card cannot be safely probed for. Instead you need to
|
| /linux/Documentation/i2c/ |
| H A D | old-module-parameters.rst | 8 safely skip this section.
|
| /linux/Documentation/power/ |
| H A D | energy-model.rst | 82 should call EM API to free it safely when it's no longer needed. The EM
229 'struct em_perf_table'. That new EM will be safely used inside the EM framework
241 It will allow the EM framework to safely remove the memory, when there is
254 call rcu_read_unlock(). In this way the EM safely uses the RCU read section
|
| /linux/Documentation/litmus-tests/ |
| H A D | README | 67 x safely outside of the critical section.
|
| /linux/Documentation/staging/ |
| H A D | magic-number.rst | 31 discipline, these cases get detected quickly and safely.
|
| /linux/Documentation/driver-api/pldmfw/ |
| H A D | index.rst | 48 In order to safely process the firmware file, care is taken to avoid
|
| /linux/Documentation/leds/ |
| H A D | leds-class-flash.rst | 79 This function can be safely called with NULL or error pointer argument.
|
| /linux/Documentation/trace/ |
| H A D | ring-buffer-map.rst | 22 be safely read by the mapper (see ring-buffer-design.rst).
|
| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A 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
|
| /linux/Documentation/infiniband/ |
| H A D | core_locking.rst | 62 example, a consumer may safely call ib_poll_cq() on multiple CPUs
|