/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/vsomeip/ |
H A D | vsomeip_3.4.10.bb | 1 SUMMARY = "The implementation of SOME/IP" 3 (Scalable service-Oriented MiddlewarE over IP (SOME/IP)) protocol."
|
/openbmc/linux/arch/x86/kernel/cpu/mce/ |
H A D | severity.c | 193 SOME, "Action optional: unknown MCACOD", 197 SOME, "Action optional with lost events", 215 SOME, "No match",
|
/openbmc/linux/tools/testing/selftests/net/ |
H A D | hwtstamp_config.c | 61 RX_FILTER(SOME),
|
/openbmc/linux/drivers/accessibility/speakup/ |
H A D | speakup.h | 25 #define SOME 0x0010 macro
|
H A D | synth.c | 495 short spk_punc_masks[] = { 0, SOME, MOST, PUNC, PUNC | B_SYM };
|
/openbmc/phosphor-pcie-presence/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/openpower-sbe-interface/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/phosphor-mboxd/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/pyphosphor/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/inarp/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/openpower-inventory-upload/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/openpower-logging/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/phosphor-event/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/boost-dbus/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/google-ipmi-sys/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/libbej/ |
H A D | MAINTAINERS | 35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
|
/openbmc/linux/Documentation/userspace-api/netlink/ |
H A D | genetlink-legacy.rst | 27 [SOME-OTHER-ATTR] 40 [SOME-OTHER-ATTR]
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | CNRI-Jython | 9 …E, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. SOME STATES DO NOT ALLOW…
|
H A D | eGenix | 16 …E, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. SOME JURISDICTIONS DO NO…
|
H A D | AFL-1.1 | 20 …ARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NO…
|
H A D | OSL-1.0 | 100 LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
|
H A D | CC-BY-ND-2.0 | 41 …URACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NO…
|
H A D | CC-BY-ND-2.5 | 41 …URACY, OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NO…
|
/openbmc/linux/Documentation/RCU/ |
H A D | whatisRCU.rst | 41 :ref:`3. WHAT ARE SOME EXAMPLE USES OF CORE RCU API? <3_whatisRCU>` 45 :ref:`5. WHAT ARE SOME SIMPLE IMPLEMENTATIONS OF RCU? <5_whatisRCU>` 414 3. WHAT ARE SOME EXAMPLE USES OF CORE RCU API? 609 5. WHAT ARE SOME SIMPLE IMPLEMENTATIONS OF RCU?
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-design-CFS.rst | 89 4. SOME FEATURES OF CFS
|