| /openbmc/docs/ |
| H A D | cpp-style-and-conventions.md | 1 # C++ Coding Style and Conventions
82 Any recommendation within the CCG of GSL conventions may be ignored at this
121 The iostream conventions of using 'operator<<' contribute to an increased code
278 ### Naming Conventions.
325 conventions (`using type = T`) while a multi-word type alias should be
327 - Exception: A library API may use lower_snake_case to match conventions of the
331 in `_t` to match the conventions of the STL.
351 - Exception: A library API may use lower_snake-case to match conventions of the
|
| /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.
136 conventions.
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.
|
| /openbmc/openbmc-test-automation/ |
| H A D | CONTRIBUTING.md | 81 underscores or case. However, our team will observe the following conventions
243 - General variable naming conventions:
321 - Special variable naming conventions.
324 conventions in order to achieve consistency throughout the code.
418 - Directory variables should follow the same conventions as file
579 - When you define a python function, observe the following conventions:
658 - General variable naming conventions:
678 - Special variable naming conventions.
681 conventions in order to achieve consistency throughout the code.
775 - Directory variables should follow the same conventions as file variables.
|
| /openbmc/linux/Documentation/bpf/standardization/ |
| H A D | abi.rst | 5 BPF ABI Recommended Conventions and Guidelines v1.0
9 conventions and guidelines for producing portable BPF program binaries.
|
| /openbmc/linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 18 .. note:: Conventions on comments and documentation are not checked by
145 This example showcases a few ``rustdoc`` features and some conventions followed
184 Rust kernel code follows the usual Rust naming conventions:
195 conventions, and namespacing introduced by modules and types should not be
|
| /openbmc/linux/include/linux/ |
| H A D | fsl_devices.h | 23 * Some conventions on how we handle peripherals on Freescale chips
39 * naming conventions:
|
| /openbmc/webui-vue/docs/ |
| H A D | readme.md | 4 heroText: Style Guide and Coding Conventions
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | entry_64.rst | 45 have different calling conventions. The syscall and sysenter
46 instructions have their own peculiar calling conventions. Some of
|
| /openbmc/u-boot/doc/ |
| H A D | README.vf610 | 6 1. CONVENTIONS FOR FUSE ASSIGNMENTS
|
| H A D | README.fsl_iim | 22 conventions used by U-Boot to store some specific data in the fuses, e.g. MAC
|
| H A D | README.mxc_ocotp | 25 conventions used by U-Boot to store some specific data in the fuses, e.g. MAC
|
| /openbmc/u-boot/doc/imx/common/ |
| H A D | imx27.txt | 6 1. CONVENTIONS FOR FUSE ASSIGNMENTS
|
| H A D | imx25.txt | 6 1. CONVENTIONS FOR FUSE ASSIGNMENTS
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Configuration/ |
| H A D | README.md | 9 with the dbus conventions used elsewhere in the project.
|
| /openbmc/linux/include/asm-generic/ |
| H A D | syscalls.h | 9 * Calling conventions for these system calls can differ, so
|
| /openbmc/linux/tools/include/nolibc/ |
| H A D | arch-x86_64.h | 25 * - see also x86-64 ABI section A.2 AMD64 Linux Kernel Conventions, A.2.1
26 * Calling Conventions.
|
| /openbmc/openbmc/meta-phosphor/recipes-support/boost/ |
| H A D | boost_%.bbappend | 11 #https://github.com/openbmc/docs/blob/master/cpp-style-and-conventions.md#boost
|
| /openbmc/linux/arch/x86/entry/ |
| H A D | thunk_64.S | 12 /* rdi: arg1 ... normal C conventions. rax is saved/restored. */
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 85 services) not following the conventions expected by the unwinder.
101 Unwinding typically relies on code following specific conventions (e.g.
103 conventions and may require special handling in the unwinder, e.g.
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libxml/ |
| H A D | libxml-sax-writer-perl_0.57.bb | 5 XML escaping conventions, and so forth. It is still considered alpha, \
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | porting.rst | 604 calling conventions for ->follow_link() have changed. Instead of returning
614 calling conventions for ->put_link() have changed. It gets inode instead of
766 ->atomic_open() calling conventions have changed. Gone is ``int *opened``,
780 users. Calling conventions: on success a reference to new struct file
908 Calling conventions for file_open_root() changed; now it takes struct path *
925 filldir_t (readdir callbacks) calling conventions have changed. Instead of
927 to) and true - "keep going" (as 0 in old calling conventions). Rationale:
936 Calling conventions for ->tmpfile() have changed. It now takes a struct
|
| /openbmc/openbmc/poky/meta/recipes-support/libffi/ |
| H A D | libffi_3.4.6.bb | 4 conventions. This allows a programmer to call any function specified by a call interface descripti…
|
| /openbmc/linux/Documentation/devicetree/bindings/openrisc/opencores/ |
| H A D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /openbmc/linux/Documentation/arch/arm/nwfpe/ |
| H A D | notes.rst | 9 will point it out. The ARM calling conventions require floating point
|
| /openbmc/docs/designs/ |
| H A D | device-tree-gpio-naming.md | 18 in the kernel device tree files. The problem is there are no naming conventions
220 Need to ensure OpenBMC device trees conform to the above naming conventions.
|