| /openbmc/webui-vue/.github/ISSUE_TEMPLATE/ |
| H A D | feature_request.md | 10 concise description of what the problem is. Ex. I'm always frustrated when [...]
12 **Describe the solution you'd like** A clear and concise description of what you
15 **Describe alternatives you've considered** A clear and concise description of
|
| H A D | bug_report.md | 9 **Describe the bug** A clear and concise description of what the bug is.
18 **Expected behavior** A clear and concise description of what you expected to
|
| /openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
| H A D | bug_report.md | 17 A clear and concise description of what unexpectedly happened.
20 A clear and concise description of what you expected to happen.
|
| /openbmc/qemu/include/qapi/ |
| H A D | error.h | 42 * failure. This can make the error checking more concise, and can
82 * This is more concise than
89 * This is more concise and fails more nicely than
96 * This is more concise than
173 * This is more concise than
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-cbor2_5.6.5.bb | 1 DESCRIPTION = "An implementation of RFC 7049 - Concise Binary Object Representation (CBOR)."
|
| /openbmc/docs/ |
| H A D | cpp-style-and-conventions.md | 15 1. Code should be clear and concise.
19 ### Code should be clear and concise
27 Modern practices allow C++ to be an expressive, but concise, language. We tend
|
| /openbmc/openbmc/poky/meta/recipes-devtools/go/ |
| H A D | go-common.inc | 3 programmers more productive. Go is expressive, concise, clean, and\
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | Create.interface.yaml | 94 Valid CBOR (Concise Binary Object Representation)
|
| /openbmc/openbmc/poky/meta/recipes-kernel/perf/perf/ |
| H A D | sort-pmuevents.py | 76 # yes, there's a more concise way to do this, but our nested dictionaries of
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-init.rst | 35 `--concise` argument.
|
| /openbmc/linux/Documentation/trace/rv/ |
| H A D | deterministic_automata.rst | 170 O'Regan, Gerard. Concise guide to software engineering. Springer,
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | printk-basics.rst | 92 Besides being more concise than the equivalent printk() calls, they can use a
|
| H A D | dma-api-howto.rst | 10 with example pseudo-code. For a concise description of the API, see
|
| /openbmc/u-boot/include/ |
| H A D | regmap.h | 31 * map, can be accessed in a concise manner.
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | sysfs.rst | 128 defining attributes easier as well as making code more concise and
|
| H A D | autofs.rst | 61 *offset* are treated identically so a concise summary is that the root
|
| /openbmc/linux/Documentation/process/ |
| H A D | 5.Posting.rst | 171 most direct and concise way possible.
|
| H A D | howto.rst | 446 clear and concise reasoning as to why those changes should not be made.
|
| H A D | coding-style.rst | 887 messages concise, clear, and unambiguous.
|
| /openbmc/linux/include/uapi/scsi/fc/ |
| H A D | fc_els.h | 41 ELS_REC = 0x13, /* read exchange concise */
468 * ELS_REC - Read exchange concise.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/perl/files/ |
| H A D | perl-rdepends.txt | 125 RDEPENDS:perl-module-b-concise += "perl-module-b"
126 RDEPENDS:perl-module-b-concise += "perl-module-b-op-private"
127 RDEPENDS:perl-module-b-concise += "perl-module-config"
128 RDEPENDS:perl-module-b-concise += "perl-module-exporter"
129 RDEPENDS:perl-module-b-concise += "perl-module-feature"
130 RDEPENDS:perl-module-b-concise += "perl-module-strict"
131 RDEPENDS:perl-module-b-concise += "perl-module-warnings"
158 RDEPENDS:perl-module-b-showlex += "perl-module-b-concise"
162 RDEPENDS:perl-module-b-terse += "perl-module-b-concise"
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A D | howto.rst | 460 modifiche o fornire delle chiare e concise motivazioni per le quali le
|
| /openbmc/u-boot/tools/buildman/ |
| H A D | README | 66 Buildman produces a concise summary of which boards succeeded and failed.
626 once. This makes the output as concise as possible. To see which boards have
|
| /openbmc/linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 493 To be concise, we call that write locks and non-recursive read locks as
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | cpuidle.rst | 463 between them is that the name is expected to be more concise, while the
|