| /openbmc/phosphor-user-manager/ |
| H A D | .clang-tidy | 3 readability-identifier-naming
7 - key: readability-identifier-naming.ClassCase
9 - key: readability-identifier-naming.EnumCase
11 - key: readability-identifier-naming.EnumConstantCase
13 - key: readability-identifier-naming.FunctionCase
15 - key: readability-identifier-naming.NamespaceCase
17 - key: readability-identifier-naming.ParameterCase
19 - key: readability-identifier-naming.StructCase
21 - key: readability-identifier-naming.VariableCase
|
| /openbmc/openbmc/poky/meta/recipes-sato/sato-icon-theme/ |
| H A D | icon-naming-utils_0.8.90.bb | 5 names specified in the Icon Naming Specification. The Icon Naming \
7 icon names proposed in the Icon Naming Specification, and generate the \
9 Naming Specification provides a standard list of common icon contexts \
11 environment or application that implements the naming specification. "
17 SRC_URI = "${DEBIAN_MIRROR}/main/i/icon-naming-utils/icon-naming-utils_${PV}.orig.tar.gz"
|
| /openbmc/docs/designs/ |
| H A D | device-tree-gpio-naming.md | 1 # Device Tree GPIO Naming in OpenBMC
18 in the kernel device tree files. The problem is there are no naming conventions
26 [patch][3] shows an example of naming the GPIOs for a system.
28 GPIOs are used for arbitrary things. It's pretty hard to have a coherent naming
32 possibilities quite a bit and allows the possibility of a naming scheme to
37 - Ensure common function GPIOs within OpenBMC use the same naming convention
42 naming convention and then the sub bullets list the common GPIO names to be used
43 (when available on an OpenBMC system). This naming convention must be followed
220 Need to ensure OpenBMC device trees conform to the above naming conventions.
|
| /openbmc/ |
| D | opengrok0.0.log | [all...] |
| /openbmc/libcper/ |
| H A D | .clang-tidy | 173 -readability-identifier-naming,
200 - key: readability-identifier-naming.FunctionCase
202 - key: readability-identifier-naming.NamespaceCase
204 - key: readability-identifier-naming.ParameterCase
206 - key: readability-identifier-naming.StructCase
208 - key: readability-identifier-naming.VariableCase
|
| /openbmc/obmc-console/ |
| H A D | .clang-tidy | 182 -readability-identifier-naming,
211 - key: readability-identifier-naming.FunctionCase
213 - key: readability-identifier-naming.NamespaceCase
215 - key: readability-identifier-naming.ParameterCase
217 - key: readability-identifier-naming.StructCase
219 - key: readability-identifier-naming.VariableCase
|
| /openbmc/libpldm/ |
| H A D | .clang-tidy | 183 -readability-identifier-naming,
212 - key: readability-identifier-naming.FunctionCase
214 - key: readability-identifier-naming.NamespaceCase
216 - key: readability-identifier-naming.ParameterCase
218 - key: readability-identifier-naming.StructCase
220 - key: readability-identifier-naming.VariableCase
|
| /openbmc/bmcweb/http/ |
| H A D | nghttp2_adapters.hpp | 19 * naming as nghttp2, so ignore naming violations.
22 // NOLINTBEGIN(readability-identifier-naming,
218 // NOLINTEND(readability-identifier-naming,
|
| /openbmc/estoraged/ |
| H A D | .clang-tidy | 273 readability-identifier-naming,
291 - key: readability-identifier-naming.ClassCase
293 - key: readability-identifier-naming.FunctionCase
295 - key: readability-identifier-naming.NamespaceCase
297 - key: readability-identifier-naming.ParameterCase
299 - key: readability-identifier-naming.StructCase
301 - key: readability-identifier-naming.VariableCase
|
| /openbmc/bmcweb/ |
| H A D | .clang-tidy | 353 readability-identifier-naming,
394 - key: readability-identifier-naming.ClassCase
396 - key: readability-identifier-naming.FunctionCase
398 - key: readability-identifier-naming.FunctionIgnoredRegexp
400 - key: readability-identifier-naming.NamespaceCase
402 - key: readability-identifier-naming.ParameterCase
404 - key: readability-identifier-naming.StructCase
406 - key: readability-identifier-naming.StructIgnoredRegexp
408 - key: readability-identifier-naming.VariableCase
|
| /openbmc/bmcweb/config/ |
| H A D | bmcweb_config.h.in | 7 // NOLINTBEGIN(readability-identifier-naming)
11 // NOLINTEND(readability-identifier-naming)
|
| /openbmc/linux/drivers/comedi/drivers/ni_routing/ |
| H A D | README | 100 easier, the naming conventions used in the [board-name].c file are
101 similar to the naming conventions as presented by NI-MAX.
171 Various naming conventions and relations:
173 These are various notes that help to relate the naming conventions used in the
174 NI-STC with those naming conventions used here.
177 Signal sources for most signals-destinations are given a specific naming
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | cpuinfo.rst | 77 Naming of Flags
83 resulting x86_cap/bug_flags[] are used to populate /proc/cpuinfo. The naming
92 b: The naming can be overridden.
101 constant. If, for some reason, the naming of X86_FEATURE_<name> changes, one
102 shall override the new naming with the name already used in /proc/cpuinfo.
104 c: The naming override can be "", which means it will not appear in /proc/cpuinfo.
|
| /openbmc/phosphor-time-manager/ |
| H A D | .clang-tidy | 278 readability-identifier-naming,
308 - key: readability-identifier-naming.ClassCase
310 - key: readability-identifier-naming.FunctionCase
312 - key: readability-identifier-naming.NamespaceCase
314 - key: readability-identifier-naming.ParameterCase
316 - key: readability-identifier-naming.StructCase
318 - key: readability-identifier-naming.VariableCase
|
| /openbmc/phosphor-led-sysfs/ |
| H A D | .clang-tidy | 279 readability-identifier-naming,
311 - key: readability-identifier-naming.ClassCase
313 - key: readability-identifier-naming.FunctionCase
315 - key: readability-identifier-naming.NamespaceCase
317 - key: readability-identifier-naming.ParameterCase
319 - key: readability-identifier-naming.StructCase
321 - key: readability-identifier-naming.VariableCase
|
| /openbmc/entity-manager/ |
| H A D | .clang-tidy | 313 readability-identifier-naming,
347 - key: readability-identifier-naming.ClassCase
349 - key: readability-identifier-naming.FunctionCase
351 - key: readability-identifier-naming.NamespaceCase
353 - key: readability-identifier-naming.ParameterCase
355 - key: readability-identifier-naming.StructCase
357 - key: readability-identifier-naming.VariableCase
|
| /openbmc/linux/include/linux/ |
| H A D | stddef.h | 43 * used normally without sub-struct naming, and the latter can be
59 * used normally without sub-struct naming, and the latter can be
75 * used normally without sub-struct naming, and the latter can be
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | README.md | 43 …[Device Tree GPIO Naming in OpenBMC document](https://github.com/openbmc/docs/blob/master/designs/…
49 …[Device Tree GPIO Naming in OpenBMC document](https://github.com/openbmc/docs/blob/master/designs/…
|
| /openbmc/dbus-sensors/ |
| H A D | .clang-tidy | 335 readability-identifier-naming,
372 - key: readability-identifier-naming.ClassCase
374 - key: readability-identifier-naming.FunctionCase
376 - key: readability-identifier-naming.NamespaceCase
378 - key: readability-identifier-naming.ParameterCase
380 - key: readability-identifier-naming.StructCase
382 - key: readability-identifier-naming.VariableCase
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/samsung/ |
| H A D | samsung-soc.yaml | 7 title: Samsung S3C, S5P and Exynos SoC compatibles naming convention
30 - description: Preferred naming style for compatibles of SoC components
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-4.3.rst | 158 Output file naming changes
162 If you rely on the existing naming (e.g. in external scripts) you may need to
163 either modify configuration or adapt to the new naming. Further details:
208 :term:`STAMP` and :term:`WORKDIR`, you may notice small directory naming and
209 stamp naming changes.
|
| /openbmc/u-boot/arch/x86/include/asm/ |
| H A D | processor.h | 36 * The naming follows Intel's naming.
|
| /openbmc/linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 181 Naming chapter
184 Rust kernel code follows the usual Rust naming conventions:
186 https://rust-lang.github.io/api-guidelines/naming.html
194 Having said that, casing should be adjusted to follow the Rust naming
|
| /openbmc/linux/Documentation/driver-api/tty/ |
| H A D | moxa-smartio.rst | 14 3.2 Device naming convention
105 3.2 Device naming convention
110 Device naming when more than 2 boards installed
113 Naming convention for each Smartio/Industio multiport board is
|
| /openbmc/linux/arch/sparc/kernel/ |
| H A D | prom_32.c | 40 /* The following routines deal with the black magic of fully naming a
50 * For children of the ROOT node, the naming convention is fixed and
181 /* "isa" is handled with platform naming */ in __build_path_component()
184 /* Use platform naming convention. */ in __build_path_component()
|