Searched full:conventions (Results 1 – 25 of 57) sorted by relevance
123
| /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.
|
| /Documentation/devicetree/bindings/openrisc/opencores/ |
| D | or1ksim.txt | 5 platform essentially follows the conventions of the OpenRISC architecture
|
| /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
|
| /Documentation/arch/arm/nwfpe/ |
| D | notes.rst | 9 will point it out. The ARM calling conventions require floating point
|
| /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
197 Rust kernel code follows the usual Rust naming conventions:
208 conventions, and namespacing introduced by modules and types should not be
|
| /Documentation/crypto/ |
| D | intro.rst | 71 all the same naming conventions of crypto_alloc\*.
|
| /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.
|
| /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
|
| /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
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | fixed-partitions.yaml | 10 This binding can be used on platforms which have strong conventions about
|
| /Documentation/driver-api/ |
| D | ioctl.rst | 20 conventions around defining them.
23 ioctl commands that follow modern conventions: ``_IO``, ``_IOR``,
|
| D | pwm.rst | 154 signal conventions in the PWM framework. By definition, normal polarity
|
| /Documentation/networking/pse-pd/ |
| D | introduction.rst | 45 following naming conventions are recommended:
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 58 Calling conventions
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra124-xusb-padctl.txt | 36 Child nodes contain the pinmux configurations following the conventions from
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 74 to have different conventions about what "active" means. Such decisions should
|
| /Documentation/arch/powerpc/ |
| D | booting.rst | 39 conventions:
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 5 This is a summary of the most important conventions for use of fault
|
| /Documentation/arch/arm/ |
| D | microchip.rst | 219 Naming conventions and best practice:
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 8 described here. It's recommended to follow these conventions whenever a
|
| /Documentation/userspace-api/ |
| D | seccomp_filter.rst | 179 architecture that supports multiple system call invocation conventions,
181 the numbers in the different calling conventions overlap, then checks in
|
| /Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 113 related code conventions in userspace, we currently allow arbitrary
|
| /Documentation/userspace-api/media/v4l/ |
| D | colorspaces.rst | 150 mix of different standards also led to very confusing naming conventions
|
| /Documentation/dev-tools/kunit/ |
| D | style.rst | 36 unsure, follow the conventions set by tests in similar areas.
|
| /Documentation/userspace-api/netlink/ |
| D | genetlink-legacy.rst | 201 conventions. For example, the following struct is 4 bytes, not 6 bytes:
|
123