| /openbmc/linux/drivers/vfio/cdx/ |
| H A D | Kconfig | 17 If you don't know what to do here, say N.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/byacc/ |
| H A D | byacc_20241231.bb | 4 # Setting to PD as this is what the upstream has it as.
|
| /openbmc/phosphor-logging/ |
| H A D | log_resolve_main.cpp | 40 std::cerr << "Unable to resolve: " << e.what() << std::endl; in main()
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | transitioning-to-a-custom-environment.rst | 12 glanced over the document :doc:`what-i-wish-id-known`, the latter contains
14 now, as you are starting your own project, it isn't exactly straightforward what
92 Add what's missing and fix anything that's broken using your knowledge of the
102 your own distribution in a new layer inheriting from Poky but overriding what
|
| H A D | what-i-wish-id-known.rst | 48 Intel, TI, NXP and others have information on what BSP layers to use with
98 function of a particular part of the workflow gives you an idea of what might
155 #. **You will want to learn about and know what's packaged in the root filesystem.**
170 * find out what packages are created by a recipe
171 * find out what files are in a package
172 * find out what files are in an image
187 #. **Depending on what you primary interests are with the Yocto Project, you
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | amd_hsmp.rst | 60 /* ERROR HANDLING; you can check errno to see what went wrong */
78 what happened. The transaction returns 0 on success.
|
| /openbmc/linux/arch/um/os-Linux/drivers/ |
| H A D | ethertap_user.c | 31 enum { ADD_ADDR, DEL_ADDR } what; member
43 change.what = op; in etap_change()
|
| /openbmc/linux/tools/testing/selftests/seccomp/ |
| H A D | seccomp_benchmark.c | 199 #define ESTIMATE(fmt, var, what) do { \ in main() argument
200 var = (what); \ in main()
|
| /openbmc/linux/kernel/irq/ |
| H A D | Kconfig | 126 If you don't know what to do here, say N.
138 If you don't know what to do here, say N.
|
| /openbmc/linux/include/linux/ |
| H A D | netfs.h | 296 enum netfs_sreq_ref_trace what);
298 bool was_async, enum netfs_sreq_ref_trace what);
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | mirror_gre_lag_lacp.sh | 216 local what=$1; shift
246 log_test "$what ($tcflags)"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/vk-gl-cts/ |
| H A D | khronos-cts.inc | 33 # probing and build what it thinks is appropriate.
45 # is going to probe the sysroot to try to figure out what to build
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | kref.rst | 124 This way, it doesn't matter what order the two threads handle the
146 Don't assume you know what you are doing and use the above construct.
147 First of all, you may not know what you are doing. Second, you may
148 know what you are doing (there are some situations where locking is
150 know what they are doing may change the code or copy the code. It's
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | debugfs-ideapad | 8 capability and what graphic component within the machine.
|
| /openbmc/phosphor-fan-presence/docs/presence/ |
| H A D | path.md | 7 the fan's inventory object path being the base path plus what's given here.
|
| /openbmc/phosphor-logging/tools/phosphor-logging/templates/ |
| H A D | elog-process-metadata.mako.cpp | 1 ## Note that this file is not auto generated, it is what generates the
|
| /openbmc/u-boot/scripts/ |
| H A D | coreboot.sed | 4 # Script to convert coreboot code to something similar to what U-Boot uses
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-hello.rst | 61 The console output tells you what version
96 While every attempt is made to explain what is happening during the
109 "Hello World". However, it is unknown what BitBake needs and what you
117 questions and helps you better understand exactly what is going on.
134 directory. Run the ``bitbake`` command and see what it does::
141 :term:`BBPATH` variable is what tells BitBake where
214 have a value similar to what OpenEmbedded and BitBake use in the default
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | inventory.md | 7 the fan's inventory object path being the base path plus what's given here.
|
| /openbmc/openbmc/meta-security/recipes-scanners/checksec/ |
| H A D | checksec_2.6.0.bb | 2 DESCRIPTION = "The checksec script is designed to test what standard Linux OS and PaX security feat…
|
| /openbmc/linux/arch/powerpc/kernel/ |
| H A D | mce_power.c | 115 static int mce_flush(int what) in mce_flush() argument
118 if (what == MCE_FLUSH_SLB) { in mce_flush()
123 if (what == MCE_FLUSH_ERAT) { in mce_flush()
127 if (what == MCE_FLUSH_TLB) { in mce_flush()
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | iforce-protocol.rst | 15 This document describes what I managed to discover about the protocol used to
17 from Immerse. That's why you should not trust what is written in this
25 send data to your I-Force device based on what you read in this document.
367 3. Play the effect, and watch what happens on the spy screen.
|
| /openbmc/docs/designs/ |
| H A D | psu-monitoring.md | 60 are present in the system, what type of power supply is present (maximum
61 output power such as 900W, 1400W, 2200W, etc.), and what type of input power
95 information, what type each supply is, etc. The application would then try to
97 would be considered invalid. The application should continue to check what if
|
| /openbmc/linux/arch/x86/mm/ |
| H A D | init.c | 892 void free_init_pages(const char *what, unsigned long begin, unsigned long end) in free_init_pages() argument
932 POISON_FREE_INITMEM, what); in free_init_pages()
941 void free_kernel_image_pages(const char *what, void *begin, void *end) in free_kernel_image_pages() argument
947 free_init_pages(what, begin_ul, end_ul); in free_kernel_image_pages()
|
| /openbmc/obmc-ikvm/ |
| H A D | ikvm_input.cpp | 95 entry("ERROR=%s", e.what())); in connect()
101 entry("ERROR=%s", e.what())); in connect()
156 entry("ERROR=%s", e.what())); in disconnect()
|