| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libstrictures/ |
| H A D | libstrictures-perl_2.000006.bb | 14 I also want to ensure that obvious coding mistakes, like indirect object \
15 syntax (and not so obvious mistakes that cause things to accidentally compile \
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A D | ia64.rst | 42 * Hardly any performance tuning has been done. Obvious targets
44 obvious targets include making sure we don't flush the TLB
|
| /openbmc/qemu/docs/specs/ |
| H A D | standard-vga.rst | 22 Applies to the pci variant only for obvious reasons.
73 Likewise applies to the pci variant only for obvious reasons.
|
| /openbmc/linux/Documentation/process/ |
| H A D | management-style.rst | 27 making it painfully obvious to the questioner that we don't have a clue
39 manager must be to make it. That's very deep and obvious, but it's not
254 don't try to make it too obvious unless you really **intend** to irritate
279 peoples mistakes, and make it painfully obvious to everybody else that
280 you're incompetent, the obvious question becomes one of why do it in the
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-toml_0.10.2.bb | 1 SUMMARY = "Python Library for Tom's Obvious, Minimal Language"
|
| /openbmc/qemu/include/hw/arm/ |
| H A D | armsse-version.h | 22 * we pick obvious numbers for the benefit of people debugging with gdb.
|
| /openbmc/openbmc/poky/bitbake/ |
| H A D | LICENSE | 20 …l modification, so the full unminified file is currently included to make it obvious where this is.
|
| /openbmc/linux/arch/mips/sni/ |
| H A D | eisa.c | 16 * Now use a platform device, since that's the obvious choice. */
|
| /openbmc/linux/drivers/eisa/ |
| H A D | virtual_root.c | 26 * Now use a platform device, since that's the obvious choice. */
|
| /openbmc/phosphor-logging/docs/ |
| H A D | structured-logging.md | 150 2. Any constant C-string may be interpreted as a key and give non-obvious
158 be obvious that the application is writing to the journal. The `lg2` APIs detect
267 universally standardized API. The `lg2` API seems obvious enough in ergonomics
|
| /openbmc/qemu/scripts/coccinelle/ |
| H A D | use-g_new-etc.cocci | 1 // Use g_new() & friends where that makes obvious sense
|
| /openbmc/openbmc/poky/bitbake/doc/ |
| H A D | README | 35 obvious reasons, we will only support building the BitBake
|
| /openbmc/linux/Documentation/arch/sh/ |
| H A D | register-banks.rst | 21 in mind when writing code that utilizes these banked registers, for obvious
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | Kconfig.recursion-issue-01 | 37 # obvious that an easy to solution to this problem should just be the removal
|
| H A D | Kconfig.recursion-issue-02 | 18 # A perhaps not so obvious implication of this is that, if semantics on these
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | modifying-patches.rst | 16 name, all enclosed in square brackets, is noticeable enough to make it obvious
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/perl/ |
| H A D | libdbi-perl_1.646.bb | 23 # source of test failure not obvious
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | ibt.h | 14 * Esp. that latter one is a bit non-obvious, but some code like compressed,
|
| /openbmc/openbmc/poky/bitbake/lib/bb/fetch2/ |
| H A D | README | 2 some of the constraints that are present. Some are obvious, some are less so. It is
|
| /openbmc/linux/Documentation/driver-api/gpio/ |
| H A D | using-gpio.rst | 6 as such are normally not user facing abstractions. The most obvious, natural
|
| /openbmc/linux/drivers/cxl/ |
| H A D | cxlpci.h | 13 * "DVSEC" redundancies removed. When obvious, abbreviations may be used.
|
| /openbmc/linux/Documentation/userspace-api/ |
| H A D | no_new_privs.rst | 6 its parent did not have. The most obvious examples are setuid/setgid
|
| /openbmc/linux/Documentation/mm/ |
| H A D | overcommit-accounting.rst | 8 Heuristic overcommit handling. Obvious overcommits of address
|
| /openbmc/linux/drivers/gpu/drm/panel/ |
| H A D | panel-samsung-atna33xc20.c | 158 * obvious if we try to enable again without a power cycle (see the in atana33xc20_disable()
186 * non-obvious. in atana33xc20_enable()
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | graph_ds_impl.rst | 110 object was ``free``'d with ``bpf_obj_drop`` the answer is obvious: the verifier
116 obvious. The verifier could enforce the same semantics as for ``bpf_obj_drop``,
|