Home
last modified time | relevance | path

Searched full:confusion (Results 1 – 25 of 220) sorted by relevance

123456789

/openbmc/openbmc/poky/meta/files/common-licenses/
H A Dxinetd25 ….2.* line; using that would only create confusion. Naming the next release 2.3.0 would put to rest…
H A DXSL30 no possibility of confusion between the derived package and this
H A DDSSSL36 no possibility of confusion between the derived package and this
H A DECL-1.040 to avoid any confusion with the Original Work of the copyright holders.
H A DSimple-2.026 … it`s a license form to use in any way that you find helpful. To avoid confusion, however, if you…
H A DSimPL-2.037 … it's a license form to use in any way that you find helpful. To avoid confusion, however, if you…
H A DGD3 In order to resolve any possible confusion regarding the authorship of gd, the following copyright …
/openbmc/linux/drivers/comedi/drivers/ni_routing/
H A DREADME11 major reasons exist why this caused major confusion for users:
56 documentation, _and_ a mitigation for confusion that has plagued the use of
155 In summary, similar confusion about signal routing configuration, albeit less,
/openbmc/linux/include/linux/mfd/
H A Docelot.h27 * prints of "invalid resource" which will simply add confusion. in ocelot_regmap_from_resource_optional()
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/ssiapi/ssiapi/
H A D0003-engine-Define-discover-const-String-path-in-base-cla.patch6 this fixes the confusion that compiler may have when inheriting two
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-class-backlight53 interface reduces the probability of confusion with
/openbmc/linux/tools/lib/perf/include/perf/
H A Dcpumap.h9 /** A wrapper around a CPU to avoid confusion with the perf_cpu_map's map's indices. */
/openbmc/linux/Documentation/networking/
H A Dx25.rst25 the Packet Layer but there would be no confusion since the class of device
/openbmc/openbmc/poky/meta/conf/machine/include/arm/
H A Darch-armv8r.inc15 # All ARMv8 has floating point hardware built in. Null it here to avoid any confusion for 32bit.
/openbmc/qemu/docs/system/
H A Dgdb.rst65 On modern kernels confusion can be caused by code being relocated by
67 confusion when debugging such things you either need to update gdb's
/openbmc/linux/drivers/staging/media/atomisp/pci/
H A Dsh_css_struct.h23 so this could cause confusion; hence the _struct
/openbmc/linux/drivers/char/xillybus/
H A Dxillybus.h39 * Read-write confusion: wr_* and rd_* notation sticks to FPGA view, so
/openbmc/qemu/include/exec/
H A Dmemattrs.h22 * confusion if different parts of QEMU used the same bit for
/openbmc/linux/tools/testing/selftests/bpf/progs/
H A Dverifier_search_pruning.c30 __description("pointer/scalar confusion in state equality check (way 1)")
55 __description("pointer/scalar confusion in state equality check (way 2)")
/openbmc/openbmc/poky/meta/recipes-graphics/mesa/files/
H A D0001-amd-Include-missing-llvm-IR-header-Module.h.patch22 confusion to compiler
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dmodule.bbclass78 # clear them out to avoid confusion
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/libmad/libmad/
H A Dadd-pkgconfig.patch8 some confusion for people installing from source and on some BSDs which
/openbmc/linux/Documentation/userspace-api/media/dvb/
H A Ddvbapi.rst17 In order to avoid confusion, within this document, it was opted to refer to
/openbmc/openbmc/poky/meta/recipes-devtools/rsync/
H A Drsync_3.4.1.bb54 # to avoid confusion as we will generate configure.
/openbmc/u-boot/include/
H A Dbootm.h28 * argc is adjusted accordingly. This avoids confusion as to how

123456789