Searched full:conventions (Results 1 – 25 of 126) sorted by relevance
123456
| /Linux-v6.1/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.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/include/linux/ |
| D | fsl_devices.h | 23 * Some conventions on how we handle peripherals on Freescale chips
39 * naming conventions:
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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
771 ->atomic_open() calling conventions have changed. Gone is ``int *opened``,
785 users. Calling conventions: on success a reference to new struct file
913 Calling conventions for file_open_root() changed; now it takes struct path *
930 filldir_t (readdir callbacks) calling conventions have changed. Instead of
932 to) and true - "keep going" (as 0 in old calling conventions). Rationale:
941 Calling conventions for ->tmpfile() have changed. It now takes a struct
|
| /Linux-v6.1/include/asm-generic/ |
| D | syscalls.h | 9 * Calling conventions for these system calls can differ, so
|
| /Linux-v6.1/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.
|
| /Linux-v6.1/arch/x86/entry/ |
| D | thunk_64.S | 12 /* rdi: arg1 ... normal C conventions. rax is saved/restored. */
|
| /Linux-v6.1/tools/include/nolibc/ |
| D | arch-x86_64.h | 61 * - see also x86-64 ABI section A.2 AMD64 Linux Kernel Conventions, A.2.1
62 * Calling Conventions.
|
| /Linux-v6.1/Documentation/devicetree/bindings/openrisc/opencores/ |
| D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /Linux-v6.1/Documentation/arm/nwfpe/ |
| D | notes.rst | 9 will point it out. The ARM calling conventions require floating point
|
| /Linux-v6.1/arch/sparc/net/ |
| D | bpf_jit_32.h | 5 /* Conventions:
|
| /Linux-v6.1/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
|
| /Linux-v6.1/include/acpi/platform/ |
| D | acintel.h | 28 * Calling conventions:
|
| /Linux-v6.1/Documentation/crypto/ |
| D | intro.rst | 71 all the same naming conventions of crypto_alloc\*.
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | ioctl.rst | 20 conventions around defining them.
23 ioctl commands that follow modern conventions: ``_IO``, ``_IOR``,
|
| /Linux-v6.1/drivers/media/i2c/ |
| D | tvp7002_reg.h | 14 /* Naming conventions
|
| /Linux-v6.1/arch/x86/include/asm/ |
| D | set_memory.h | 64 * set_memory_* function for more details on conventions.
|
| /Linux-v6.1/arch/powerpc/include/asm/ |
| D | dcr-native.h | 75 /* R/W of indirect DCRs make use of standard naming conventions for DCRs */
|
| /Linux-v6.1/Documentation/devicetree/bindings/mtd/partitions/ |
| D | fixed-partitions.yaml | 10 This binding can be used on platforms which have strong conventions about
|
| /Linux-v6.1/arch/powerpc/kernel/ |
| D | sys_ppc32.c | 3 * sys_ppc32.c: 32-bit system calls with complex calling conventions.
|
| /Linux-v6.1/Documentation/driver-api/gpio/ |
| D | legacy.rst | 5 This provides an overview of GPIO access conventions on Linux.
58 GPIO conventions
486 What do these conventions omit?
488 One of the biggest things these conventions omit is pin multiplexing, since
|
| /Linux-v6.1/arch/m68k/include/asm/ |
| D | bootstd.h | 34 /* Calling conventions compatible to (uC)linux/68k
|
| /Linux-v6.1/Documentation/driver-api/usb/ |
| D | callbacks.rst | 58 Calling conventions
|
| /Linux-v6.1/Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra124-xusb-padctl.txt | 36 Child nodes contain the pinmux configurations following the conventions from
|
123456
