| /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.
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.
177 Signal sources for most signals-destinations are given a specific naming
|
| /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.
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.
177 Signal sources for most signals-destinations are given a specific naming
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | cpuinfo.rst | 77 Naming of Flags
83 resulting x86_cap/bug_flags[] are used to populate /proc/cpuinfo. The naming
92 b: The naming can be overridden.
101 constant. If, for some reason, the naming of X86_FEATURE_<name> changes, one
102 shall override the new naming with the name already used in /proc/cpuinfo.
104 c: The naming override can be "", which means it will not appear in /proc/cpuinfo.
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | cpuinfo.rst | 77 Naming of Flags
83 resulting x86_cap/bug_flags[] are used to populate /proc/cpuinfo. The naming
92 b: The naming can be overridden.
101 constant. If, for some reason, the naming of X86_FEATURE_<name> changes, one
102 shall override the new naming with the name already used in /proc/cpuinfo.
104 c: The naming override can be "", which means it will not appear in /proc/cpuinfo.
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | stddef.h | 43 * used normally without sub-struct naming, and the latter can be
59 * used normally without sub-struct naming, and the latter can be
75 * used normally without sub-struct naming, and the latter can be
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | stddef.h | 47 * used normally without sub-struct naming, and the latter can be
63 * used normally without sub-struct naming, and the latter can be
79 * used normally without sub-struct naming, and the latter can be
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/samsung/ |
| D | samsung-soc.yaml | 7 title: Samsung S3C, S5P and Exynos SoC compatibles naming convention
30 - description: Preferred naming style for compatibles of SoC components
|
| /kernel/linux/linux-6.6/Documentation/rust/ |
| D | coding-guidelines.rst | 181 Naming chapter
184 Rust kernel code follows the usual Rust naming conventions:
186 https://rust-lang.github.io/api-guidelines/naming.html
194 Having said that, casing should be adjusted to follow the Rust naming
|
| /kernel/linux/linux-6.6/arch/sparc/kernel/ |
| D | prom_32.c | 40 /* The following routines deal with the black magic of fully naming a
50 * For children of the ROOT node, the naming convention is fixed and
181 /* "isa" is handled with platform naming */ in __build_path_component()
184 /* Use platform naming convention. */ in __build_path_component()
|
| /kernel/linux/linux-5.10/arch/sparc/kernel/ |
| D | prom_32.c | 40 /* The following routines deal with the black magic of fully naming a
50 * For children of the ROOT node, the naming convention is fixed and
181 /* "isa" is handled with platform naming */ in __build_path_component()
184 /* Use platform naming convention. */ in __build_path_component()
|
| /kernel/linux/linux-6.6/Documentation/driver-api/tty/ |
| D | moxa-smartio.rst | 14 3.2 Device naming convention
105 3.2 Device naming convention
110 Device naming when more than 2 boards installed
113 Naming convention for each Smartio/Industio multiport board is
|
| /kernel/linux/linux-5.10/tools/lib/bpf/ |
| D | README.rst | 3 libbpf API naming convention
7 functions and types. Every group has its own naming convention
85 API documentation above. See API naming convention to choose the right
|
| /kernel/linux/linux-6.6/security/tomoyo/ |
| D | util.c | 432 * Check whether the given string follows the naming rules.
433 * Returns true if @string follows the naming rules, false otherwise.
515 * Check whether the given string follows the naming rules.
516 * Returns true if @string follows the naming rules, false otherwise.
524 * tomoyo_correct_path2 - Check whether the given pathname follows the naming rules.
529 * Returns true if @filename follows the naming rules, false otherwise.
544 * Check whether the given pathname follows the naming rules.
545 * Returns true if @filename follows the naming rules, false otherwise.
553 * tomoyo_correct_domain - Check whether the given domainname follows the naming rules.
557 * Returns true if @domainname follows the naming rules, false otherwise.
|
| /kernel/linux/linux-5.10/security/tomoyo/ |
| D | util.c | 432 * Check whether the given string follows the naming rules.
433 * Returns true if @string follows the naming rules, false otherwise.
510 * Check whether the given string follows the naming rules.
511 * Returns true if @string follows the naming rules, false otherwise.
519 * tomoyo_correct_path2 - Check whether the given pathname follows the naming rules.
524 * Returns true if @filename follows the naming rules, false otherwise.
539 * Check whether the given pathname follows the naming rules.
540 * Returns true if @filename follows the naming rules, false otherwise.
548 * tomoyo_correct_domain - Check whether the given domainname follows the naming rules.
552 * Returns true if @domainname follows the naming rules, false otherwise.
|
| /kernel/linux/linux-6.6/tools/testing/selftests/futex/ |
| D | README | 51 Naming
53 o FIXME: decide on a sane test naming scheme. Currently the tests are named
|
| /kernel/linux/linux-5.10/tools/testing/selftests/futex/ |
| D | README | 51 Naming
53 o FIXME: decide on a sane test naming scheme. Currently the tests are named
|
| /kernel/linux/linux-6.6/Documentation/bpf/libbpf/ |
| D | libbpf_naming_convention.rst | 3 API naming convention
7 functions and types. Every group has its own naming convention
68 API documentation above. See API naming convention to choose the right
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/ |
| D | qcom-soc.yaml | 7 title: Qualcomm SoC compatibles naming convention
33 # Preferred naming style for compatibles of SoC components:
|
| /kernel/uniproton/src/include/uapi/ |
| D | prt_fs.h | 63 * Partition naming rules:
66 * The partition naming rules is:
|
| /kernel/linux/linux-5.10/Documentation/driver-api/serial/ |
| D | moxa-smartio.rst | 21 3.3 Device naming convention
162 3.3 Device naming convention
175 which is named "ttyMxx". For callout port, the naming convention
178 Device naming when more than 2 boards installed
181 Naming convention for each Smartio/Industio multiport board is
244 naming.
458 If you'd like to use other device names instead of default naming
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/netlink/ |
| D | c-code-gen.rst | 10 to control the naming.
67 If naming is desired ``enum-name`` can be used to specify the name.
|
| /kernel/linux/linux-5.10/drivers/staging/rtl8192e/ |
| D | TODO | 2 * clean up function naming
|
| /kernel/linux/config/ |
| D | README.md | 68 …Place the patches for the chip component in the corresponding path based on the path and naming ru…
77 …e for the chip component in the corresponding path based on the path and naming rules of the chip …
|
| /kernel/linux/build/ |
| D | README.md | 59 …Place the patches for the chip component in the corresponding path based on the path and naming ru…
68 …e for the chip component in the corresponding path based on the path and naming rules of the chip …
|
| /kernel/linux/linux-5.10/drivers/clk/ti/ |
| D | clkctrl.c | 266 /* l4per-clkctrl:1234:0 style naming based on clkctrl_name */ in clkctrl_get_clock_name()
278 /* l4per:1234:0 old style naming based on clkctrl_name */ in clkctrl_get_clock_name()
283 /* l4per_cm:1234:0 old style naming based on parent node name */ in clkctrl_get_clock_name()
288 /* l4per-clkctrl:1234:0 style naming based on node name */ in clkctrl_get_clock_name()
613 * specific compatible proprerty and standard clock node naming in _ti_omap4_clkctrl_setup()
|