| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Message.v1_3_0.json | 68 …"description": "Used to provide suggestions on how to resolve the situation that caused the messag…
74 … "description": "The list of recommended steps to resolve the situation that caused the message.",
78 …his property shall contain an array of recommended steps to resolve the situation that caused the …
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Message.v1_3_0.json | 68 …"description": "Used to provide suggestions on how to resolve the situation that caused the messag…
74 … "description": "The list of recommended steps to resolve the situation that caused the message.",
78 …his property shall contain an array of recommended steps to resolve the situation that caused the …
|
| /openbmc/linux/Documentation/timers/ |
| H A D | timers-howto.rst | 70 will obviously depend on your specific situation, but
100 tolerances here are very situation specific, thus it
|
| /openbmc/phosphor-debug-collector/ |
| H A D | ramoops_manager.cpp | 67 // This is a best-effort logging situation so don't throw anything in createError()
72 // This is a best-effort logging situation so don't throw anything in createError()
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | rcubarrier.rst | 54 This situation can be handled by the rcu_barrier() primitive. Rather
166 Is there any other situation where rcu_barrier() might
296 Is there any other situation where rcu_barrier() might
302 RCU in a filesystem, which resulted in a similar situation at
|
| /openbmc/linux/lib/ |
| H A D | Kconfig.kgdb | 141 kernel is still usable in this situation.
143 No guarantees that the kernel is still usable in this situation.
|
| /openbmc/linux/Documentation/tools/rtla/ |
| H A D | rtla-hwnoise.rst | 78 The tool should report *0* hardware-related noise in the ideal situation.
82 the ideal situation in the same hardware::
|
| /openbmc/linux/Documentation/process/ |
| H A D | volatile-considered-harmful.rst | 61 Another situation where one might be tempted to use volatile is
96 type of situation.
|
| H A D | 3.Early-stage.rst | 51 The reality of the situation was different; the kernel developers were far
188 idea. The best thing to do in this situation is to proceed, keeping the
217 designed to help with this sort of situation; more information can be found
|
| /openbmc/linux/drivers/usb/serial/ |
| H A D | aircable.c | 22 * situation, when too much data arrives to the device because it sends the data
23 * but with out the header. I will use a simply hack to override this situation,
|
| /openbmc/linux/drivers/rapidio/switches/ |
| H A D | idt_gen3.c | 220 * If the link is up (PORT_OK) - situation is handled as *new* device insertion.
226 * TODO: This is not sufficient in a situation when a link between two devices
227 * was down and up again (e.g. cable disconnect). For that situation full ackID
|
| /openbmc/linux/include/linux/regulator/ |
| H A D | driver.h | 91 * current situation detection. Detection can be configured for three
96 * - REGULATOR_SEVERITY_ERR should indicate that over-current situation is
100 * - REGULATOR_SEVERITY_WARN should indicate situation where hardware is
107 * voltage situation detection. Detection can be configured for same
110 * under voltage situation detection. Detection can be configured for same
113 * temperature situation detection.Detection can be configured for same
|
| /openbmc/linux/Documentation/admin-guide/aoe/ |
| H A D | todo.rst | 8 free page is needed for the sk_buff allocation. This situation has
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/stressapptest/ |
| H A D | stressapptest_1.0.11.bb | 5 situation in order to test the existing hardware devices in a computer. \
|
| /openbmc/linux/tools/perf/util/ |
| H A D | sharded_mutex.h | 9 * In a situation where a lock is needed per object, having a mutex can be
|
| /openbmc/linux/drivers/bcma/ |
| H A D | README | 17 In this situation we decided to introduce separated bus. It can contain up to
|
| /openbmc/linux/drivers/accessibility/speakup/ |
| H A D | TODO | 13 has been able to find a situation which produces it consistently.
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | fixed-link.txt | 8 Such a fixed link situation is described by creating a 'fixed-link'
|
| /openbmc/u-boot/doc/ |
| H A D | README.displaying-bmps | 2 the following might be relevant to your situation...
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Bahyph | 7 …above has been notified of the possibility of such damages. If any such situation arises, you resp…
|
| H A D | NIST-Software | 26 used in any situation where a failure could cause risk of injury or damage to
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/zeroconf/zeroconf/ |
| H A D | debian-zeroconf | 22 # or only want zeroconf in a fallback situation
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libcapture/ |
| H A D | libcapture-tiny-perl_0.50.bb | 7 a dozen capturing modules to use in any particular situation and just use \
|
| /openbmc/linux/kernel/module/ |
| H A D | dups.c | 78 * The typical situation is a module successully loaded. In that in kmod_dup_request_delete()
79 * situation the module will be present already in userspace. If in kmod_dup_request_delete()
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | cpu-idle-cooling.rst | 7 Situation:
17 Another situation is when the silicon temperature continues to
|