Home
last modified time | relevance | path

Searched full:appear (Results 1 – 25 of 2473) sorted by relevance

12345678910>>...99

/kernel/linux/linux-6.6/arch/arm/include/uapi/asm/
Dbyteorder.h6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
Dswab.h6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
/kernel/linux/linux-5.10/arch/arm/include/uapi/asm/
Dbyteorder.h6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
Dswab.h6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
/kernel/linux/linux-6.6/arch/arm/include/asm/
Dswab.h6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
/kernel/linux/linux-5.10/arch/arm/include/asm/
Dswab.h6 * that byte accesses appear as:
8 * and word accesses (data or instruction) appear as:
11 * When in big endian mode, byte accesses appear as:
13 * and word accesses (data or instruction) appear as:
/kernel/linux/linux-6.6/Documentation/filesystems/
Dconfigfs.rst23 appear in sysfs, allowing userspace to read the attributes via
30 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
50 subsystems. Once a client subsystem is loaded, it will appear as a
55 appear at this time. readdir(3) can determine what the attributes are,
175 By itself, a config_item cannot do much more than appear in configfs.
219 When a config_item wants an attribute to appear as a file in the item's
223 attribute file will appear with the configfs_attribute->ca_name
243 appear as the contents of a file in the item's configfs directory.
246 attribute file will appear with the configfs_bin_attribute->cb_attr.ca_name
345 tells configfs to make the subsystem appear in the file tree::
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/
Dconfigfs.rst23 appear in sysfs, allowing userspace to read the attributes via
30 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
50 subsystems. Once a client subsystem is loaded, it will appear as a
55 appear at this time. readdir(3) can determine what the attributes are,
175 By itself, a config_item cannot do much more than appear in configfs.
219 When a config_item wants an attribute to appear as a file in the item's
223 attribute file will appear with the configfs_attribute->ca_name
243 appear as the contents of a file in the item's configfs directory.
246 attribute file will appear with the configfs_bin_attribute->cb_attr.ca_name
346 tells configfs to make the subsystem appear in the file tree::
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/stable/
Dsysfs-driver-aspeed-vuart5 will appear on the host <-> BMC LPC bus.
13 the UART will appear on the host <-> BMC LPC bus.
/kernel/linux/linux-5.10/Documentation/ABI/stable/
Dsysfs-driver-aspeed-vuart5 will appear on the host <-> BMC LPC bus.
13 the UART will appear on the host <-> BMC LPC bus.
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/ptp/
Dtimestamper.txt41 appear on time stamp channel 0 (zero), and those from phy@2 appear on
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/ptp/
Dtimestamper.txt41 appear on time stamp channel 0 (zero), and those from phy@2 appear on
/kernel/linux/linux-6.6/net/sunrpc/auth_gss/
Dgss_krb5_unseal.c18 * that both that copyright notice and this permission notice appear in
47 * notice appear in all copies and that both that copyright notice and
48 * this permission notice appear in supporting documentation, and that
Dgss_krb5_seal.c19 * that both that copyright notice and this permission notice appear in
48 * notice appear in all copies and that both that copyright notice and
49 * this permission notice appear in supporting documentation, and that
/kernel/linux/linux-6.6/include/drm/
Ddrm_modeset_helper.h6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
Ddrm_blend.h6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
/kernel/linux/linux-5.10/include/drm/
Ddrm_modeset_helper.h6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
Ddrm_blend.h6 * the above copyright notice appear in all copies and that both that copyright
7 * notice and this permission notice appear in supporting documentation, and
/kernel/linux/linux-5.10/include/asm-generic/bitops/
Dinstrumented-non-atomic.h91 * can appear to succeed but actually fail.
105 * can appear to succeed but actually fail.
119 * can appear to succeed but actually fail.
/kernel/linux/linux-6.6/include/linux/
Dcoda.h33 notice and this permission notice appear in all copies of the
35 thereof, and that both notices appear in supporting documentation, and
/kernel/linux/linux-5.10/include/linux/
Dcoda.h33 notice and this permission notice appear in all copies of the
35 thereof, and that both notices appear in supporting documentation, and
/kernel/linux/linux-6.6/include/asm-generic/bitops/
Dinstrumented-non-atomic.h94 * can appear to succeed but actually fail.
109 * can appear to succeed but actually fail.
124 * can appear to succeed but actually fail.
/kernel/linux/linux-6.6/arch/arm/mach-omap2/
Dcm3xxx.h26 * These registers appear once per CM module.
38 * These register offsets generally appear in more than one PRCM submodule.
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dcm3xxx.h26 * These registers appear once per CM module.
38 * These register offsets generally appear in more than one PRCM submodule.
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/haswell/
Duncore-interconnect.json3 …cker queue from allocation till deallocation. Aperture requests (snoops) appear as NC decoded inte…
7 …cker queue from allocation till deallocation. Aperture requests (snoops) appear as NC decoded inte…

12345678910>>...99