Home
last modified time | relevance | path

Searched full:naming (Results 1 – 25 of 224) sorted by relevance

123456789

/openbmc/phosphor-user-manager/
H A D.clang-tidy3 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 Dicon-naming-utils_0.8.90.bb5 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/phosphor-power/phosphor-power-sequencer/docs/
H A Dnamed_gpios.md10 [Device Tree GPIO Naming in OpenBMC](https://github.com/openbmc/docs/blob/master/designs/device-tre…
27 [Device Tree GPIO Naming in OpenBMC](https://github.com/openbmc/docs/blob/master/designs/device-tre…
/openbmc/docs/designs/
H A Ddevice-tree-gpio-naming.md1 # 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/bmcweb/config/
H A Dbmcweb_config.h.in7 // NOLINTBEGIN(readability-identifier-naming)
11 // NOLINTEND(readability-identifier-naming)
/openbmc/
Dopengrok0.0.log[all...]
/openbmc/libcper/
H A D.clang-tidy173 -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/bmcweb/http/
H A Dnghttp2_adapters.hpp19 * naming as nghttp2, so ignore naming violations.
22 // NOLINTBEGIN(readability-identifier-naming,
224 // NOLINTEND(readability-identifier-naming,
/openbmc/obmc-console/
H A D.clang-tidy182 -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-tidy183 -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/u-boot/arch/x86/include/asm/
H A Dprocessor.h36 * The naming follows Intel's naming.
/openbmc/bmcweb/
H A D.clang-tidy314 readability-identifier-naming,
355 - key: readability-identifier-naming.ClassCase
357 - key: readability-identifier-naming.FunctionCase
359 - key: readability-identifier-naming.FunctionIgnoredRegexp
361 - key: readability-identifier-naming.NamespaceCase
363 - key: readability-identifier-naming.ParameterCase
365 - key: readability-identifier-naming.StructCase
367 - key: readability-identifier-naming.StructIgnoredRegexp
369 - key: readability-identifier-naming.VariableCase
/openbmc/estoraged/
H A D.clang-tidy273 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/dbus-sensors/
H A D.clang-tidy296 readability-identifier-naming,
333 - key: readability-identifier-naming.ClassCase
335 - key: readability-identifier-naming.FunctionCase
337 - key: readability-identifier-naming.NamespaceCase
339 - key: readability-identifier-naming.ParameterCase
341 - key: readability-identifier-naming.StructCase
343 - key: readability-identifier-naming.VariableCase
/openbmc/phosphor-time-manager/
H A D.clang-tidy278 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-tidy279 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-tidy313 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/openbmc/poky/documentation/migration-guides/
H A Dmigration-4.3.rst158 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/phosphor-virtual-sensor/
H A D.clang-tidy3 readability-identifier-naming
/openbmc/x86-power-control/
H A D.clang-tidy3 readability-identifier-naming
/openbmc/phosphor-net-ipmid/
H A D.clang-tidy3 readability-identifier-naming
/openbmc/qemu/tests/qapi-schema/
H A Dalternate-clash.json2 # Naming rules make collision impossible (even with the pragma). If
H A Dunion-bad-discriminator.json1 # we require the discriminator to be a string naming a base-type member
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/pptp-linux/pptp-linux/
H A Doptions.pptp19 # (option naming specific to ppp 2.4.0 with unofficial patch)
/openbmc/openbmc/poky/meta/conf/machine/include/powerpc/
H A DREADME12 However, a general naming scheme should be similar to: ppc[64][<family>][-nf].

123456789