| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | vxlan_bridge_1q_ipv6.sh | 668 local what=$1; shift
675 log_test "VXLAN: $what"
705 local what=$1; shift
714 log_test "VXLAN: $what"
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | instantiating-devices.rst | 7 I2C bus segment, and what address these devices are using. For this
211 kernels will find out that this method 3 is essentially similar to what
233 what addresses they live at. However, in certain cases, it does not, so a
272 available, and you don't need to know what driver the device needs.
|
| /openbmc/linux/tools/testing/selftests/net/mptcp/ |
| H A D | mptcp_sockopt.c | 791 static int rcheck(int wstatus, const char *what) in rcheck() argument
796 fprintf(stderr, "%s exited, status=%d\n", what, WEXITSTATUS(wstatus)); in rcheck()
799 xerror("%s killed by signal %d\n", what, WTERMSIG(wstatus)); in rcheck()
801 xerror("%s stopped by signal %d\n", what, WSTOPSIG(wstatus)); in rcheck()
|
| /openbmc/linux/Documentation/usb/ |
| H A D | gadget_configfs.rst | 24 Creating a gadget means deciding what configurations there will be
314 which can be read-only or read-write, depending on what they represent.
341 two functions to decide what they actually do.
391 4. Each USB function naturally has its own view of what it wants
|
| /openbmc/linux/Documentation/trace/ |
| H A D | tracepoint-analysis.rst | 15 what is going on within the system. There are a large number of methods for
68 call. The following is an example that reports every 5 seconds what processes
148 to know what the standard deviation is. By and large, this is left to the
223 There may also be a requirement to identify what functions within a program
|
| /openbmc/linux/Documentation/locking/ |
| H A D | robust-futex-ABI.rst | 11 The interesting data as to what futexes a thread is holding is kept on a
14 kernel intervention required for robust_futexes above and beyond what is
61 address of the associated 'lock entry', plus or minus, of what will
104 robust_futex mechanism doesn't care what else is in that structure, so
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/ti/ |
| H A D | tlan.rst | 76 interface. This is also what to do if you want to use the BNC
85 to force 100Mbs operation. (I'm not sure what will happen
|
| /openbmc/docs/designs/ |
| H A D | thermal-control-modes.md | 50 available thermal control modes along with what current mode is in use.
73 The thermal control application used must be configured to provide what thermal
|
| H A D | nmi-dbus-interface.md | 20 there is no way to figure out what went wrong with the host in a hung state. One
88 is initiated irrespective of what host OS state is in, so it has minimal impact
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | ocfs2-online-filecheck.rst | 56 1. If you want to know what error exactly happened to <inode> before fixing, do::
68 <ERROR> says what kind of errors was found. For the detailed error numbers,
|
| /openbmc/linux/Documentation/timers/ |
| H A D | timers-howto.rst | 80 msleep(1~20) may not do what the caller intends, and
98 be balanced with what is an acceptable upper bound on
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | rdma.rst | 83 what is configured by user for a given cgroup and what is supported by
|
| /openbmc/openbmc/poky/meta/recipes-extended/bash/ |
| H A D | bash.inc | 15 # This is what other major distros do. And this is what we wanted. See bug#5359 and bug#7137.
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | processor.h | 711 void free_init_pages(const char *what, unsigned long begin, unsigned long end);
712 extern void free_kernel_image_pages(const char *what, void *begin, void *end);
|
| /openbmc/openpower-vpd-parser/vpd-manager/src/ |
| H A D | ddimm_parser.cpp | 323 std::string(l_ex.what())); in getDdr4BasedDdimmSize()
395 logging::logMessage(exp.what()); in parse()
|
| /openbmc/openbmc/poky/meta/recipes-graphics/vulkan/ |
| H A D | vulkan-loader_1.3.296.0.bb | 41 # The tags versions should always be sdk-x.y.z, as this is what
|
| /openbmc/google-misc/subprojects/nemora-postd/ |
| H A D | README.md | 57 what you set via `busctl`.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-connectivity/netplan/ |
| H A D | netplan_1.1.1.bb | 4 interfaces and what each should be configured to do. From this description \
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | index.rst | 18 what-i-wish-id-known
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | berlin,pinctrl.txt | 13 Be aware the Marvell Berlin datasheets use the keyword 'mode' for what
|
| /openbmc/linux/fs/9p/ |
| H A D | Kconfig | 30 If you don't know what Access Control Lists are, say N
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe-get-info.rst | 45 Capabilities describe what a frontend can do. Some capabilities are
|
| /openbmc/openbmc/meta-security/recipes-security/libgssglue/files/ |
| H A D | libgssglue-canon-name.patch | 7 what __gss_copy_namebuf does is to alloc memory for a gss_buffer_desc and \
|
| /openbmc/openpower-pnor-code-mgmt/ |
| H A D | item_updater_main.cpp | 134 log<level::ERR>(e.what()); in main()
|
| /openbmc/linux/tools/testing/selftests/tc-testing/ |
| H A D | TODO.txt | 3 - Determine what tc features are supported in the kernel. If features are not
|