Searched full:conventions (Results 1 – 25 of 256) sorted by relevance
1234567891011
| /kernel/linux/linux-5.10/drivers/staging/comedi/drivers/ni_routing/ |
| 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.
|
| /kernel/linux/linux-6.6/drivers/comedi/drivers/ni_routing/ |
| 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.
|
| /kernel/linux/linux-6.6/Documentation/bpf/standardization/ |
| D | abi.rst | 5 BPF ABI Recommended Conventions and Guidelines v1.0
9 conventions and guidelines for producing portable BPF program binaries.
|
| /kernel/linux/linux-6.6/Documentation/rust/ |
| 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
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | fsl_devices.h | 23 * Some conventions on how we handle peripherals on Freescale chips
39 * naming conventions:
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | fsl_devices.h | 23 * Some conventions on how we handle peripherals on Freescale chips
39 * naming conventions:
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | entry_64.rst | 45 have different calling conventions. The syscall and sysenter
46 instructions have their own peculiar calling conventions. Some of
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | entry_64.rst | 45 have different calling conventions. The syscall and sysenter
46 instructions have their own peculiar calling conventions. Some of
|
| /kernel/linux/linux-6.6/include/asm-generic/ |
| D | syscalls.h | 9 * Calling conventions for these system calls can differ, so
|
| /kernel/linux/linux-5.10/include/asm-generic/ |
| D | syscalls.h | 9 * Calling conventions for these system calls can differ, so
|
| /kernel/linux/linux-6.6/tools/include/nolibc/ |
| D | arch-x86_64.h | 25 * - see also x86-64 ABI section A.2 AMD64 Linux Kernel Conventions, A.2.1
26 * Calling Conventions.
|
| /kernel/linux/linux-6.6/Documentation/livepatch/ |
| 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.
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| 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
|
| /kernel/linux/linux-6.6/arch/x86/entry/ |
| D | thunk_64.S | 12 /* rdi: arg1 ... normal C conventions. rax is saved/restored. */
|
| /kernel/linux/linux-5.10/arch/x86/entry/ |
| D | thunk_64.S | 12 /* rdi: arg1 ... normal C conventions. rax is saved/restored. */
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/openrisc/opencores/ |
| D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/openrisc/opencores/ |
| D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /kernel/linux/linux-5.10/Documentation/arm/nwfpe/ |
| D | notes.rst | 9 will point it out. The ARM calling conventions require floating point
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/nwfpe/ |
| D | notes.rst | 9 will point it out. The ARM calling conventions require floating point
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra124-dpaux-padctl.txt | 17 Child nodes contain the pinmux configurations following the conventions
|
| /kernel/linux/linux-6.6/arch/sparc/net/ |
| D | bpf_jit_32.h | 5 /* Conventions:
|
| /kernel/linux/linux-5.10/arch/sparc/net/ |
| D | bpf_jit_32.h | 5 /* Conventions:
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | asm-annotations.rst | 76 standard C calling conventions. For example, on x86, this means that the
110 conventions -- global and local. Like in C, they both align the functions to
|
| /kernel/linux/linux-5.10/include/acpi/platform/ |
| D | acintel.h | 28 * Calling conventions:
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| 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
|
1234567891011