| /OK3568_Linux_fs/kernel/drivers/staging/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
|
| /OK3568_Linux_fs/kernel/Documentation/x86/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/include/linux/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/arch/sparc/kernel/ |
| H A 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()
|
| 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()
|
| /OK3568_Linux_fs/kernel/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.
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.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/as.html/ |
| H A D | PDP_002d11_002dMnemonics.html | 69 <a name="Instruction-Naming-1"></a>
70 <h4 class="subsection">9.34.4 Instruction Naming</h4>
72 <a name="index-PDP_002d11-instruction-naming"></a>
|
| H A D | s390-Register.html | 69 <a name="Register-naming"></a>
70 <h4 class="subsubsection">9.41.3.1 Register naming</h4>
72 <a name="index-s390-register-naming"></a>
|
| H A D | i386_002dMnemonics.html | 71 <a name="Instruction-Naming"></a>
72 <h4 class="subsubsection">9.16.4.1 Instruction Naming</h4>
74 <a name="index-i386-instruction-naming"></a>
76 <a name="index-x86_002d64-instruction-naming"></a>
168 ‘<samp>cqto</samp>’ in AT&T naming. <code>as</code> accepts either naming for these
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/as.html/ |
| H A D | PDP_002d11_002dMnemonics.html | 69 <a name="Instruction-Naming-1"></a>
70 <h4 class="subsection">9.34.4 Instruction Naming</h4>
72 <a name="index-PDP_002d11-instruction-naming"></a>
|
| H A D | s390-Register.html | 69 <a name="Register-naming"></a>
70 <h4 class="subsubsection">9.41.3.1 Register naming</h4>
72 <a name="index-s390-register-naming"></a>
|
| H A D | i386_002dMnemonics.html | 71 <a name="Instruction-Naming"></a>
72 <h4 class="subsubsection">9.16.4.1 Instruction Naming</h4>
74 <a name="index-i386-instruction-naming"></a>
76 <a name="index-x86_002d64-instruction-naming"></a>
168 ‘<samp>cqto</samp>’ in AT&T naming. <code>as</code> accepts either naming for these
|
| /OK3568_Linux_fs/kernel/tools/lib/bpf/ |
| H A 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
|
| /OK3568_Linux_fs/u-boot/arch/x86/include/asm/ |
| H A D | processor.h | 37 * The naming follows Intel's naming.
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/yocto/poky/documentation/migration-guides/ |
| H A D | migration-1.3.rst | 178 .. _1.3-linux-kernel-naming:
180 Linux Kernel Naming
183 The naming scheme for kernel output binaries has been changed to now
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/serial/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/drivers/clk/ti/ |
| H A 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()
|
| /OK3568_Linux_fs/buildroot/dl/sox/git/lpc10/ |
| H A D | lpcenc.c | 12 * all lpc10 functions have more consistent naming with each other.
47 * all lpc10 functions have more consistent naming with each other.
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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.
|
| /OK3568_Linux_fs/kernel/drivers/staging/rtl8192e/ |
| H A D | TODO | 2 * clean up function naming
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Config-Names.html | 74 script are based on a three-part naming scheme, but some short predefined
75 aliases are also supported. The full naming scheme encodes three pieces
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Config-Names.html | 74 script are based on a three-part naming scheme, but some short predefined
75 aliases are also supported. The full naming scheme encodes three pieces
|