Home
last modified time | relevance | path

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

12345678910>>...12

/linux/drivers/comedi/drivers/ni_routing/
H A 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/include/linux/
H A 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/Documentation/arch/x86/
H A 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/Documentation/devicetree/bindings/arm/samsung/
H A Dsamsung-soc.yaml7 title: Samsung S3C, S5P and Exynos SoC compatibles naming convention
30 - description: Preferred naming style for compatibles of SoC components
/linux/Documentation/driver-api/tty/
H A 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/arch/sparc/kernel/
H A Dprom_32.c38 /* The following routines deal with the black magic of fully naming a in prom_early_alloc()
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()
/linux/security/tomoyo/
H A 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/Documentation/bpf/libbpf/
H A 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/tools/testing/selftests/futex/
H A DREADME51 Naming
53 o FIXME: decide on a sane test naming scheme. Currently the tests are named
/linux/Documentation/devicetree/bindings/soc/renesas/
H A Drenesas-soc.yaml7 title: Renesas SoC compatibles naming convention
38 # Preferred naming style for compatibles of SoC components
/linux/drivers/clk/ti/
H A 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/Documentation/networking/pse-pd/
H A Dintroduction.rst41 Kernel Naming Convention Recommendations
45 following naming conventions are recommended:
/linux/Documentation/admin-guide/
H A 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/Documentation/devicetree/bindings/powerpc/fsl/
H A 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/Documentation/filesystems/
H A 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/Documentation/ABI/removed/
H A Ddevfs6 races, contains a naming policy within the kernel that is
/linux/Documentation/devicetree/bindings/gpio/
H A 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/fs/sysfs/
H A DKconfig18 delegating policy decisions, like persistently naming devices.
/linux/arch/um/kernel/
H A Dumid.c36 " is used for naming the pid file and management console socket.\n\n"
/linux/Documentation/leds/
H A Duleds.rst23 any valid sysfs device node name, but consider using the LED class naming
/linux/drivers/gpu/drm/ttm/tests/
H A DTODO11 - Agree on the naming convention
/linux/Documentation/hwmon/
H A Dpowr1220.rst32 The input naming convention is as follows:
/linux/Documentation/dev-tools/kunit/
H A Dstyle.rst72 a way of categorizing test suites and naming modules which provides a
136 naming. It is a good idea to make your test functions `static` to avoid
/linux/Documentation/networking/
H A Dalias.rst19 Alias creation is done by 'magic' interface naming: eg. to create a
/linux/tools/testing/selftests/ftrace/test.d/kprobe/
H A Dkprobe_eventname.tc3 # description: Kprobe event auto/manual naming

12345678910>>...12