| /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.
|
| /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.
|
| /linux/include/linux/ |
| H A D | fsl_devices.h | 23 * Some conventions on how we handle peripherals on Freescale chips
39 * naming conventions:
|
| /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
|
| /linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 18 .. note:: Conventions on comments and documentation are not checked by
232 This example showcases a few ``rustdoc`` features and some conventions followed
301 Rust kernel code follows the usual Rust naming conventions:
312 conventions, and namespacing introduced by modules and types should not be
|
| /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.
|
| /linux/Documentation/devicetree/bindings/openrisc/opencores/ |
| H A D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /linux/Documentation/arch/arm/nwfpe/ |
| H A D | notes.rst | 9 will point it out. The ARM calling conventions require floating point
|
| /linux/arch/sparc/net/ |
| H A D | bpf_jit_32.h | 5 /* Conventions:
|
| /linux/Documentation/core-api/ |
| H A D | asm-annotations.rst | 77 standard C calling conventions. For example, on x86, this means that the
111 conventions -- global and local. Like in C, they both align the functions to
|
| /linux/Documentation/crypto/ |
| H A D | intro.rst | 71 all the same naming conventions of crypto_alloc\*.
|
| /linux/tools/arch/x86/lib/ |
| H A D | memset_64.S | 25 * from the compiler for better calling conventions.
|
| H A D | memcpy_64.S | 25 * from the compiler for better calling conventions.
|
| /linux/Documentation/driver-api/ |
| H A D | ioctl.rst | 20 conventions around defining them.
23 ioctl commands that follow modern conventions: ``_IO``, ``_IOR``,
|
| /linux/drivers/media/i2c/ |
| H A D | tvp7002_reg.h | 14 /* Naming conventions
|
| /linux/arch/x86/include/asm/ |
| H A D | cfi.h | 14 * An overview of the various calling conventions...
|
| /linux/arch/powerpc/include/asm/ |
| H A D | dcr-native.h | 75 /* R/W of indirect DCRs make use of standard naming conventions for DCRs */
|
| /linux/tools/include/nolibc/ |
| H A D | arch-x86.h | 196 * - see also x86-64 ABI section A.2 AMD64 Linux Kernel Conventions, A.2.1
197 * Calling Conventions.
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | introduction.rst | 45 following naming conventions are recommended:
|
| /linux/arch/x86/entry/ |
| H A D | calling.h | 36 For 32-bit we have the following conventions - kernel is built with
432 /* rdi: arg1 ... normal C conventions. rax is saved/restored. */
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | nvidia,tegra124-xusb-padctl.txt | 36 Child nodes contain the pinmux configurations following the conventions from
|
| /linux/Documentation/driver-api/usb/ |
| H A D | callbacks.rst | 58 Calling conventions
|
| /linux/arch/m68k/include/asm/ |
| H A D | bootstd.h | 34 /* Calling conventions compatible to (uC)linux/68k
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | intro.rst | 74 to have different conventions about what "active" means. Such decisions should
|
| /linux/Documentation/i2c/ |
| H A D | fault-codes.rst | 5 This is a summary of the most important conventions for use of fault
|