| /openbmc/linux/Documentation/nvme/ |
| H A D | feature-and-quirk-policy.rst | 7 This file explains the policy used to decide what is supported by the
8 Linux NVMe driver and what is not.
|
| /openbmc/openbmc/meta-raspberrypi/recipes-kernel/bluez-firmware-rpidistro/ |
| H A D | bluez-firmware-rpidistro_git.bb | 12 # Rather than make assumptions about what's supposed to be what, we'll
|
| /openbmc/u-boot/doc/ |
| H A D | README.multi-dtb-fit | 16 The selection is done using board_fit_config_name_match() (same as what the SPL
37 FIT (same as what the SPL uses to select the DTB for U-Boot).
|
| /openbmc/linux/fs/reiserfs/ |
| H A D | dir.c | 51 #define store_ih(where,what) copy_item_head (where, what) argument
|
| /openbmc/linux/Documentation/process/ |
| H A D | 8.Conclusion.rst | 60 project is no more than the sum of what its contributors put into it. The
63 working to make it better. The kernel is a premier example of what can be
|
| H A D | volatile-considered-harmful.rst | 15 to suppress optimization, which is almost never what one really wants to
40 compiler might think it knows what will be in shared_data, but the
101 volatile should take a step back and think about what they are truly trying
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | ip6gre_inner_v6_multipath.sh | 255 local what=$1; shift
278 multipath_eval "$what" $weight1 $weight2 $d111 $d222
|
| H A D | ip6gre_inner_v4_multipath.sh | 255 local what=$1; shift
277 multipath_eval "$what" $weight1 $weight2 $d111 $d222
|
| /openbmc/openbmc/meta-security/recipes-ids/samhain/files/ |
| H A D | samhain-samhainrc.patch | 9 accurately reflect what will be found, and
10 what will be of concern, on a OE install.
|
| /openbmc/linux/sound/sparc/ |
| H A D | cs4231.c | 443 unsigned int what, int on) in cs4231_dma_trigger() argument
448 if (what & CS4231_PLAYBACK_ENABLE) { in cs4231_dma_trigger()
460 if (what & CS4231_RECORD_ENABLE) { in cs4231_dma_trigger()
483 unsigned int what = 0; in snd_cs4231_trigger() local
489 what |= CS4231_PLAYBACK_ENABLE; in snd_cs4231_trigger()
492 what |= CS4231_RECORD_ENABLE; in snd_cs4231_trigger()
499 cs4231_dma_trigger(substream, what, 1); in snd_cs4231_trigger()
500 chip->image[CS4231_IFACE_CTRL] |= what; in snd_cs4231_trigger()
502 cs4231_dma_trigger(substream, what, 0); in snd_cs4231_trigger()
503 chip->image[CS4231_IFACE_CTRL] &= ~what; in snd_cs4231_trigger()
|
| /openbmc/openpower-proc-control/ |
| H A D | proc_control.cpp | 110 log<level::ERR>("exception raised", entry("EXCEPTION=%s", e.what())); in main()
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/onig/onig/ |
| H A D | 0002-build-enable-serial-tests-automake-option-for-ptest.patch | 14 former being what we want.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-security/softhsm/files/ |
| H A D | 0001-avoid-unnecessary-check-for-sqlite3-binary.patch | 35 AC_MSG_CHECKING(what are the SQLite3 includes)
|
| /openbmc/phosphor-post-code-manager/src/ |
| H A D | main.cpp | 82 phosphor::logging::log<phosphor::logging::level::ERR>(e.what()); in main()
|
| /openbmc/phosphor-ipmi-flash/bmc/version-handler/ |
| H A D | version_handlers_builder.cpp | 113 e.what()); in buildHandlerFromJson()
|
| /openbmc/sdbusplus/tools/sdbusplus/templates/ |
| H A D | error.hpp.mako | 30 const char* what() const noexcept override
|
| /openbmc/phosphor-pid-control/dbus/ |
| H A D | dbushelper.hpp | 65 log::entry("WHAT=%s", ex.what())); in getProperty()
|
| /openbmc/openpower-debug-collector/dump/ |
| H A D | dump_collect_main.cpp | 91 std::cerr << "Failed to collect dump: " << e.what() << std::endl; in main()
|
| /openbmc/linux/Documentation/ |
| H A D | Kconfig | 18 The files under Documentation/ABI should follow what's
|
| /openbmc/linux/Documentation/devicetree/bindings/net/can/ |
| H A D | ti_hecc.txt | 4 This file provides information, what the device node
|
| /openbmc/phosphor-logging/phosphor-rsyslog-config/ |
| H A D | server-conf.hpp | 59 log<level::ERR>(e.what()); in Server()
|
| /openbmc/phosphor-fan-presence/cooling-type/ |
| H A D | main.cpp | |
| /openbmc/linux/Documentation/admin-guide/laptops/ |
| H A D | sony-laptop.rst | 18 subsystem. See the logs of /proc/bus/input/devices to find out what those
150 Your mission, should you accept it, is to try finding out what
152 files and find out what is the impact on your laptop.
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | faq.rst | 30 For the most part, the KUnit core framework (what we use to write the tests)
67 KUnit is not working, what should I do?
89 around, so you can see what config was used after running ``kunit.py run``.
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | drm-usage-stats.rst | 90 larger value within a reasonable period. Upon observing a value lower than what
111 larger value within a reasonable period. Upon observing a value lower than what
121 time active without considering what frequency the engine is operating as a
|