| /kernel/linux/linux-4.19/fs/nls/ |
| D | Kconfig | 43 native language character sets. These character sets are stored
45 codepage if you want to be able to read/write these filenames on
55 native language character sets. These character sets are stored
57 codepage if you want to be able to read/write these filenames on
67 native language character sets. These character sets are stored
69 codepage if you want to be able to read/write these filenames on
80 native language character sets. These character sets are stored in
82 codepage if you want to be able to read/write these filenames on
96 native language character sets. These character sets are stored in
98 codepage if you want to be able to read/write these filenames on
[all …]
|
| /kernel/linux/linux-5.10/fs/nls/ |
| D | Kconfig | 44 native language character sets. These character sets are stored
46 codepage if you want to be able to read/write these filenames on
56 native language character sets. These character sets are stored
58 codepage if you want to be able to read/write these filenames on
68 native language character sets. These character sets are stored
70 codepage if you want to be able to read/write these filenames on
81 native language character sets. These character sets are stored in
83 codepage if you want to be able to read/write these filenames on
97 native language character sets. These character sets are stored in
99 codepage if you want to be able to read/write these filenames on
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
44 Every file in these directories will contain the following information:
56 important to get feedback for these interfaces to make
|
| /kernel/linux/linux-5.10/Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
44 Every file in these directories will contain the following information:
56 important to get feedback for these interfaces to make
|
| /kernel/linux/linux-5.10/arch/h8300/include/asm/ |
| D | pgtable.h | 6 #define PAGE_NONE __pgprot(0) /* these mean nothing to NO_MM */
7 #define PAGE_SHARED __pgprot(0) /* these mean nothing to NO_MM */
8 #define PAGE_COPY __pgprot(0) /* these mean nothing to NO_MM */
9 #define PAGE_READONLY __pgprot(0) /* these mean nothing to NO_MM */
10 #define PAGE_KERNEL __pgprot(0) /* these mean nothing to NO_MM */
29 * These would be in other places but having them here reduces the diffs.
|
| /kernel/linux/linux-4.19/arch/h8300/include/asm/ |
| D | pgtable.h | 9 #define PAGE_NONE __pgprot(0) /* these mean nothing to NO_MM */
10 #define PAGE_SHARED __pgprot(0) /* these mean nothing to NO_MM */
11 #define PAGE_COPY __pgprot(0) /* these mean nothing to NO_MM */
12 #define PAGE_READONLY __pgprot(0) /* these mean nothing to NO_MM */
13 #define PAGE_KERNEL __pgprot(0) /* these mean nothing to NO_MM */
32 * These would be in other places but having them here reduces the diffs.
|
| /kernel/linux/linux-4.19/drivers/staging/iio/Documentation/ |
| D | overview.txt | 12 devices. In some cases there is considerable overlap between these and
23 * Event chrdevs. These are similar to input in that they provide a
30 Note: A given device may have one or more event channel. These events are
34 fifo / ring buffers on the sensor chip. These greatly reduce the load
42 external signal (trigger). These triggers might be a data ready
45 capture or reading from a number of sensors. These triggers are
|
| /kernel/linux/linux-5.10/include/linux/sunrpc/ |
| D | metrics.h | 11 * These statistics are not for detailed problem diagnosis, but simply
14 * These counters are not meant to be human-readable, but are meant to be
23 * arrays per-CPU because these counters are always modified behind locks.
39 * These counters give an idea about how many request
51 * These count how many bytes are sent and received for a
53 * particular procedure is putting on the network. These
71 * These statuses usually indicate error conditions.
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | pointer-authentication.rst | 30 A subset of these instructions have been allocated from the HINT
32 these instructions behave as NOPs. Applications and libraries using
33 these instructions operate correctly regardless of the presence of the
85 user_pac_address_keys and struct user_pac_generic_keys). These can be
94 requesting these two separate cpu features to be enabled. The current KVM
96 these userspace flags are checked before enabling pointer authentication.
98 if support is added in the future to allow these two features to be
105 Additionally, when these vcpu feature flags are not set then KVM will
|
| /kernel/linux/linux-5.10/arch/mips/include/uapi/asm/ |
| D | mman.h | 13 * Protections are chosen from these bits, OR'd together. The
40 /* These are linux-specific */
75 #define MADV_WILLNEED 3 /* will need these pages */
76 #define MADV_DONTNEED 4 /* don't need these pages */
78 /* common parameters: try to keep these consistent across architectures */
80 #define MADV_REMOVE 9 /* remove these pages & resources */
98 #define MADV_COLD 20 /* deactivate these pages */
99 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /kernel/linux/linux-5.10/fs/jffs2/ |
| D | LICENCE | 21 macros or inline functions from these files, or you compile these
22 files and link them with other works to produce a work based on these
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
|
| /kernel/linux/linux-4.19/fs/jffs2/ |
| D | LICENCE | 21 macros or inline functions from these files, or you compile these
22 files and link them with other works to produce a work based on these
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
|
| /kernel/linux/linux-4.19/Documentation/RCU/ |
| D | rcu.txt | 22 barriers. The fact that these operations are quite expensive
32 Therefore, as soon as a CPU is seen passing through any of these
41 counters. These counters allow limited types of blocking within
44 critical sections. These variants of RCU detect grace periods
45 by sampling these counters.
76 Of these, one was allowed to lapse by the assignee, and the
91 o What are all these files in this directory?
|
| /kernel/linux/linux-4.19/drivers/scsi/arm/ |
| D | Kconfig | 10 Acorn system with one of these, say Y. If unsure, say N.
50 Acorn system with one of these, say Y. If unsure, say N.
57 system with one of these, say Y, otherwise say N.
64 you have one of these, say Y. If unsure, say N.
75 Acorn system with one of these, say Y. If unsure, say N.
83 system with one of these, say Y. If unsure, say N.
|
| /kernel/linux/linux-5.10/drivers/scsi/arm/ |
| D | Kconfig | 11 Acorn system with one of these, say Y. If unsure, say N.
51 Acorn system with one of these, say Y. If unsure, say N.
58 system with one of these, say Y, otherwise say N.
65 you have one of these, say Y. If unsure, say N.
76 Acorn system with one of these, say Y. If unsure, say N.
84 system with one of these, say Y. If unsure, say N.
|
| /kernel/linux/linux-5.10/arch/xtensa/include/uapi/asm/ |
| D | mman.h | 19 * Protections are chosen from these bits, OR'd together. The
47 /* These are linux-specific */
84 #define MADV_WILLNEED 3 /* will need these pages */
85 #define MADV_DONTNEED 4 /* don't need these pages */
87 /* common parameters: try to keep these consistent across architectures */
89 #define MADV_REMOVE 9 /* remove these pages & resources */
106 #define MADV_COLD 20 /* deactivate these pages */
107 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 4 strings for open-source SiFive IP blocks. HDL for these IP blocks
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
26 match on these IP block-specific compatible strings.
|
| /kernel/linux/linux-4.19/arch/powerpc/include/asm/nohash/32/ |
| D | pte-8xx.h | 9 * needed for the TLB and tablewalk. These definitions require Mx_CTR.PPM = 0,
16 * the TLB entry (24 and 25) for these indicators. Although the level 1
18 * set these at the page level since they get copied from the Mx_TWC
21 * These will get masked from the level 2 descriptor at TLB load time, and
28 * software no longer assumes these are only pointers.
38 /* These 4 software bits must be masked out when the L2 entry is loaded
|
| /kernel/linux/linux-5.10/Documentation/security/ |
| D | self-protection.rst | 26 is uncommon that all these goals can be met, but it is worth explicitly
27 mentioning them, since these aspects need to be explored, dealt with,
44 to redirect execution flow. To reduce the availability of these targets
54 alternatives, breakpoints, kprobes, etc. If these must exist in a
64 Most architectures have these options on by default and not user selectable.
65 For some architectures like arm that wish to have these be selectable,
75 tables, file/network/etc operation structures, etc). The number of these
83 For variables that are initialized once at ``__init`` time, these can
87 What remains are variables that are updated rarely (e.g. GDT). These
98 access userspace memory without explicit expectation to do so. These
[all …]
|
| /kernel/linux/linux-4.19/Documentation/security/ |
| D | self-protection.rst | 26 is uncommon that all these goals can be met, but it is worth explicitly
27 mentioning them, since these aspects need to be explored, dealt with,
44 to redirect execution flow. To reduce the availability of these targets
54 alternatives, breakpoints, kprobes, etc. If these must exist in a
64 Most architectures have these options on by default and not user selectable.
65 For some architectures like arm that wish to have these be selectable,
75 tables, file/network/etc operation structures, etc). The number of these
83 For variables that are initialized once at ``__init`` time, these can
87 What remains are variables that are updated rarely (e.g. GDT). These
98 access userspace memory without explicit expectation to do so. These
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | abi-testing.rst | 11 Userspace programs can start to rely on these interfaces, but they must
12 be aware of changes that can occur before these interfaces move to
15 Programs that use these interfaces are strongly encouraged to add their
16 name to the description of these interfaces, so that the kernel
|
| /kernel/linux/linux-4.19/include/linux/sunrpc/ |
| D | metrics.h | 11 * These statistics are not for detailed problem diagnosis, but simply
14 * These counters are not meant to be human-readable, but are meant to be
23 * arrays per-CPU because these counters are always modified behind locks.
39 * These counters give an idea about how many request
51 * These count how many bytes are sent and received for a
53 * particular procedure is putting on the network. These
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | intel-iommu.rst | 30 PS2 emulation. The regions of memory used for these devices are marked
32 regions will fail. Hence BIOS uses RMRR to specify these regions along with
33 devices that need to access these regions. OS is expected to setup
34 unity mappings for these regions for these devices to access these regions.
49 but these are not global address spaces, but separate for each domain.
|