Searched full:naming (Results 1 – 25 of 530) sorted by relevance
12345678910>>...22
| /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-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-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-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-4.19/arch/sparc/kernel/ |
| D | prom_32.c | 44 /* The following routines deal with the black magic of fully naming a
54 * For children of the ROOT node, the naming convention is fixed and
190 /* "isa" is handled with platform naming */ in __build_path_component()
193 /* Use platform naming convention. */ in __build_path_component()
|
| /kernel/linux/linux-4.19/Documentation/serial/ |
| D | moxa-smartio | 15 3.3 Device naming convention
102 3.3 Device naming convention
154 3.3 Device naming convention
165 which is named "ttyMxx". For callout port, the naming convention
168 Device naming when more than 2 boards installed
170 Naming convention for each Smartio/Industio multiport board is
224 naming.
393 If you'd like to use other device names instead of default naming
|
| /kernel/linux/linux-4.19/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-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-4.19/Documentation/filesystems/ |
| D | adfs.txt | 68 file type information, a file naming convention was devised (initially
71 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /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-4.19/drivers/staging/rtl8192e/ |
| D | TODO | 2 * clean up function naming
|
| /kernel/linux/linux-5.10/drivers/staging/rtl8192e/ |
| D | TODO | 2 * clean up function naming
|
| /kernel/linux/linux-4.19/security/tomoyo/ |
| D | util.c | 422 * Check whether the given string follows the naming rules.
423 * Returns true if @string follows the naming rules, false otherwise.
499 * Check whether the given string follows the naming rules.
500 * Returns true if @string follows the naming rules, false otherwise.
512 * Check whether the given pathname follows the naming rules.
513 * Returns true if @filename follows the naming rules, false otherwise.
521 * tomoyo_correct_domain - Check whether the given domainname follows the naming rules.
525 * Returns true if @domainname follows the naming rules, false otherwise.
|
| /kernel/linux/build/ |
| D | README.md | 54 …Place the patches for the chip component in the corresponding path based on the path and naming ru…
63 …e for the chip component in the corresponding path based on the path and naming rules of the chip …
|
| /kernel/linux/patches/ |
| D | README.md | 69 …Place the patches for the chip component in the corresponding path based on the path and naming ru…
78 …e for the chip component in the corresponding path based on the path and naming rules of the chip …
|
| /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/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()
275 /* l4per:1234:0 old style naming based on clkctrl_name */ in clkctrl_get_clock_name()
280 /* l4per_cm:1234:0 old style naming based on parent node name */ in clkctrl_get_clock_name()
285 /* l4per-clkctrl:1234:0 style naming based on node name */ in clkctrl_get_clock_name()
606 * specific compatible proprerty and standard clock node naming in _ti_omap4_clkctrl_setup()
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| 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.
|
| /kernel/linux/linux-4.19/Documentation/leds/ |
| D | leds-class.txt | 41 LED Device Naming
50 overhead, I suggest these become part of the device name. The naming scheme
|
| /kernel/linux/linux-5.10/Documentation/ABI/removed/ |
| D | devfs | 6 races, contains a naming policy within the kernel that is
|
| /kernel/linux/linux-4.19/Documentation/ABI/removed/ |
| D | devfs | 6 races, contains a naming policy within the kernel that is
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/powerpc/fsl/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | devices.rst | 37 and can use ``sysfs`` and ``udev`` (``systemd``) to handle the naming needs.
172 naming and use of the various types of TTYs. Note that the naming
263 the System V/Unix98 naming scheme for PTYs, which assigns a common
|
12345678910>>...22