Home
last modified time | relevance | path

Searched full:naming (Results 1 – 25 of 342) sorted by relevance

12345678910>>...14

/linux-6.12.1/drivers/comedi/drivers/ni_routing/
DREADME100 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-6.12.1/include/linux/
Dstddef.h43 * 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-6.12.1/Documentation/arch/x86/
Dcpuinfo.rst124 Naming of Flags
130 resulting x86_cap/bug_flags[] are used to populate /proc/cpuinfo. The naming
139 b: The naming can be overridden.
148 constant. If, for some reason, the naming of X86_FEATURE_<name> changes, one
149 shall override the new naming with the name already used in /proc/cpuinfo.
151 c: The naming override can be "", which means it will not appear in /proc/cpuinfo.
/linux-6.12.1/Documentation/devicetree/bindings/arm/samsung/
Dsamsung-soc.yaml7 title: Samsung S3C, S5P and Exynos SoC compatibles naming convention
30 - description: Preferred naming style for compatibles of SoC components
/linux-6.12.1/Documentation/rust/
Dcoding-guidelines.rst194 Naming chapter
197 Rust kernel code follows the usual Rust naming conventions:
199 https://rust-lang.github.io/api-guidelines/naming.html
207 Having said that, casing should be adjusted to follow the Rust naming
/linux-6.12.1/arch/sparc/kernel/
Dprom_32.c40 /* 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()
Dprom_64.c45 /* 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-6.12.1/Documentation/driver-api/tty/
Dmoxa-smartio.rst14 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-6.12.1/security/tomoyo/
Dutil.c432 * 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-6.12.1/tools/testing/selftests/futex/
DREADME51 Naming
53 o FIXME: decide on a sane test naming scheme. Currently the tests are named
/linux-6.12.1/Documentation/bpf/libbpf/
Dlibbpf_naming_convention.rst3 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-6.12.1/Documentation/devicetree/bindings/soc/renesas/
Drenesas-soc.yaml7 title: Renesas SoC compatibles naming convention
38 # Preferred naming style for compatibles of SoC components
/linux-6.12.1/Documentation/devicetree/bindings/arm/
Dqcom-soc.yaml7 title: Qualcomm SoC compatibles naming convention
33 # Preferred naming style for compatibles of SoC components:
/linux-6.12.1/Documentation/userspace-api/netlink/
Dc-code-gen.rst10 to control the naming.
67 If naming is desired ``enum-name`` can be used to specify the name.
/linux-6.12.1/Documentation/networking/pse-pd/
Dintroduction.rst41 Kernel Naming Convention Recommendations
45 following naming conventions are recommended:
/linux-6.12.1/drivers/clk/ti/
Dclkctrl.c258 /* 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-6.12.1/drivers/mfd/
Drohm-bd96801.c13 * usage or working around (or accepting a presense of) a naming conflict
29 * which implements a workaround to debugFS naming conflict and some of
34 * STBY configuration support or a proper fix to the debugFS naming
/linux-6.12.1/Documentation/filesystems/
Dadfs.rst101 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-6.12.1/Documentation/devicetree/bindings/powerpc/fsl/
Dmpc5200.txt7 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-6.12.1/Documentation/admin-guide/
Ddevices.rst36 and can use ``sysfs`` and ``udev`` (``systemd``) to handle the naming needs.
171 naming and use of the various types of TTYs. Note that the naming
262 the System V/Unix98 naming scheme for PTYs, which assigns a common
/linux-6.12.1/Documentation/ABI/removed/
Ddevfs6 races, contains a naming policy within the kernel that is
/linux-6.12.1/fs/sysfs/
DKconfig18 delegating policy decisions, like persistently naming devices.
/linux-6.12.1/drivers/staging/rtl8192e/
DTODO4 * clean up function naming
/linux-6.12.1/arch/um/kernel/
Dumid.c36 " is used for naming the pid file and management console socket.\n\n"
/linux-6.12.1/Documentation/devicetree/bindings/gpio/
Dnvidia,tegra186-gpio.yaml41 Tegra HW documentation describes a unified naming convention for all GPIOs
55 that file, the naming convention for ports matches the HW documentation.

12345678910>>...14