| /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.
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
|
| /linux/drivers/platform/wmi/ |
| H A D | Kconfig | 28 bool "Use legacy WMI device naming scheme"
30 Say Y here to force the WMI driver core to use the old WMI device naming
|
| /linux/Documentation/devicetree/bindings/arm/samsung/ |
| H A 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
|
| /linux/arch/sparc/kernel/ |
| H A D | prom_32.c | 38 /* The following routines deal with the black magic of fully naming a
48 * For children of the ROOT node, the naming convention is fixed and
179 /* "isa" is handled with platform naming */ in __build_path_component()
182 /* Use platform naming convention. */ in __build_path_component()
|
| H A D | prom_64.c | 45 /* The following routines deal with the black magic of fully naming a
55 * For children of the ROOT node, the naming convention is fixed and
348 /* "isa" is handled with platform naming */ in __build_path_component()
351 /* Use platform naming convention. */ in __build_path_component()
|
| /linux/Documentation/driver-api/tty/ |
| H A 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
|
| /linux/include/linux/ |
| H A 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
|
| /linux/security/tomoyo/ |
| H A 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.
|
| /linux/Documentation/bpf/libbpf/ |
| H A 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
|
| /linux/tools/testing/selftests/futex/ |
| H A D | README | 51 Naming
53 o FIXME: decide on a sane test naming scheme. Currently the tests are named
|
| /linux/Documentation/arch/x86/ |
| H A D | cpuinfo.rst | 127 Naming of Flags
133 resulting x86_cap/bug_flags[] are used to populate /proc/cpuinfo. The naming
155 constant. If, for some reason, the naming of X86_FEATURE_<name> changes, one
156 shall override the new naming with the name already used in /proc/cpuinfo.
|
| /linux/Documentation/devicetree/bindings/soc/renesas/ |
| H A D | renesas-soc.yaml | 7 title: Renesas SoC compatibles naming convention
38 # Preferred naming style for compatibles of SoC components
|
| /linux/lib/crypto/tests/ |
| H A D | Kconfig | 79 # included, for consistency with the naming used elsewhere (e.g. CRYPTO_SHA256).
90 # included, for consistency with the naming used elsewhere (e.g. CRYPTO_SHA512).
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | qcom-soc.yaml | 7 title: Qualcomm SoC compatibles naming convention
35 # Preferred naming style for compatibles of SoC components:
|
| /linux/drivers/clk/ti/ |
| H A D | clkctrl.c | 258 /* l4per-clkctrl:1234:0 style naming based on clkctrl_name */ in clkctrl_get_clock_name()
270 /* l4per:1234:0 old style naming based on clkctrl_name */ in clkctrl_get_clock_name()
275 /* l4per_cm:1234:0 old style naming based on parent node name */ in clkctrl_get_clock_name()
280 /* l4per-clkctrl:1234:0 style naming based on node name */ in clkctrl_get_clock_name()
602 * specific compatible property and standard clock node naming in _ti_omap4_clkctrl_setup()
|
| /linux/Documentation/userspace-api/netlink/ |
| H A D | c-code-gen.rst | 10 to control the naming.
69 If naming is desired ``enum-name`` can be used to specify the name.
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | introduction.rst | 41 Kernel Naming Convention Recommendations
45 following naming conventions are recommended:
|
| /linux/Documentation/admin-guide/ |
| H A D | devices.rst | 36 and can use ``sysfs`` and ``udev`` (``systemd``) to handle the naming needs.
173 naming and use of the various types of TTYs. Note that the naming
264 the System V/Unix98 naming scheme for PTYs, which assigns a common
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | mpc5200.txt | 7 Naming conventions
40 avoid naming conflicts with non-psc devices providing the same
50 board will have this node, and as such there is a common naming
|
| /linux/Documentation/filesystems/ |
| H A D | adfs.rst | 101 file type information, a file naming convention was devised (initially
104 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 298 Naming chapter
301 Rust kernel code follows the usual Rust naming conventions:
303 https://rust-lang.github.io/api-guidelines/naming.html
311 Having said that, casing should be adjusted to follow the Rust naming
|
| /linux/Documentation/ABI/removed/ |
| H A D | devfs | 6 races, contains a naming policy within the kernel that is
|
| /linux/drivers/gpu/drm/tyr/ |
| H A D | tyr.rs | 6 //! naming their GPUs after Nordic mythological figures and places.
|
| /linux/fs/sysfs/ |
| H A D | Kconfig | 18 delegating policy decisions, like persistently naming devices.
|
| /linux/arch/um/kernel/ |
| H A D | umid.c | 36 " is used for naming the pid file and management console socket.\n\n"
|