Home
last modified time | relevance | path

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

12345678910>>...13

/Linux-v6.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-v6.1/Documentation/x86/
Dcpuinfo.rst77 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.
/Linux-v6.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-v6.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-v6.1/Documentation/rust/
Dcoding-guidelines.rst181 Naming section in Coding Guidelines
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
/Linux-v6.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-v6.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-v6.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-v6.1/tools/testing/selftests/futex/
DREADME51 Naming
53 o FIXME: decide on a sane test naming scheme. Currently the tests are named
/Linux-v6.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-v6.1/drivers/staging/rtl8192e/
DTODO2 * clean up function naming
/Linux-v6.1/drivers/clk/ti/
Dclkctrl.c257 /* l4per-clkctrl:1234:0 style naming based on clkctrl_name */ in clkctrl_get_clock_name()
266 /* l4per:1234:0 old style naming based on clkctrl_name */ in clkctrl_get_clock_name()
271 /* l4per_cm:1234:0 old style naming based on parent node name */ in clkctrl_get_clock_name()
276 /* l4per-clkctrl:1234:0 style naming based on node name */ in clkctrl_get_clock_name()
594 * specific compatible property and standard clock node naming in _ti_omap4_clkctrl_setup()
/Linux-v6.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-v6.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-v6.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-v6.1/Documentation/ABI/removed/
Ddevfs6 races, contains a naming policy within the kernel that is
/Linux-v6.1/fs/sysfs/
DKconfig18 delegating policy decisions, like persistently naming devices.
/Linux-v6.1/arch/ia64/include/asm/
Dtypes.h7 * avoid naming clashes.
/Linux-v6.1/arch/um/kernel/
Dumid.c36 " is used for naming the pid file and management console socket.\n\n"
/Linux-v6.1/arch/ia64/include/uapi/asm/
Dtypes.h7 * avoid naming clashes.
/Linux-v6.1/Documentation/leds/
Duleds.rst23 any valid sysfs device node name, but consider using the LED class naming
Dleds-class.rst41 LED Device Naming
114 overhead, I suggest these become part of the device name. The naming scheme
/Linux-v6.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.
/Linux-v6.1/Documentation/hwmon/
Dpowr1220.rst32 The input naming convention is as follows:

12345678910>>...13