Searched full:_ (Results 1 – 25 of 215) sorted by relevance
123456789
| /Documentation/filesystems/ext4/ |
| D | super.rst | 30 - \_\_le32
34 - \_\_le32
38 - \_\_le32
42 - \_\_le32
46 - \_\_le32
50 - \_\_le32
55 - \_\_le32
59 - \_\_le32
64 - \_\_le32
68 - \_\_le32
[all …]
|
| D | group_descr.rst | 54 - \_\_le32
58 - \_\_le32
62 - \_\_le32
66 - \_\_le16
70 - \_\_le16
74 - \_\_le16
78 - \_\_le16
82 - \_\_le32
86 - \_\_le16
90 - \_\_le16
[all …]
|
| D | checksums.rst | 23 indexes. If you \_ignore\_ this step, your directories will not be
38 - \_\_le32
42 - \_\_le32
45 - \_\_le32
49 - \_\_le32
53 - \_\_le32
57 - \_\_le32
61 - \_\_le32 or \_\_le16
65 - \_\_le32
69 - \_\_le16
|
| D | inodes.rst | 41 - \_\_le16
45 - \_\_le16
49 - \_\_le32
53 - \_\_le32
59 - \_\_le32
66 - \_\_le32
73 - \_\_le32
77 - \_\_le16
81 - \_\_le16
91 - \_\_le32
[all …]
|
| D | journal.rst | 109 - \_\_be32
113 - \_\_be32
118 - \_\_be32
173 - \_\_be32
177 - \_\_be32
181 - \_\_be32
189 - \_\_be32
193 - \_\_be32
198 - \_\_be32
206 - \_\_be32
[all …]
|
| D | directory.rst | 45 - \_\_le32
49 - \_\_le16
53 - \_\_le16
77 - \_\_le32
81 - \_\_le16
85 - \_\_u8
89 - \_\_u8
141 - \_\_le32
145 - \_\_le16
149 - \_\_u8
[all …]
|
| D | mmp.rst | 43 - \_\_le32
47 - \_\_le32
51 - \_\_le64
63 - \_\_le16
67 - \_\_le16
71 - \_\_le32[226]
75 - \_\_le32
|
| D | attributes.rst | 41 - \_\_le32
58 - \_\_le32
62 - \_\_le32
66 - \_\_le32
70 - \_\_le32
74 - \_\_le32
78 - \_\_u32
103 - \_\_u8
107 - \_\_u8
111 - \_\_le16
[all …]
|
| D | ifork.rst | 79 - \_\_le16
83 - \_\_le16
87 - \_\_le16
91 - \_\_le16
99 - \_\_le32
115 - \_\_le32
119 - \_\_le32
125 - \_\_le16
129 - \_\_u16
145 - \_\_le32
[all …]
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 9 Usage of Performance Counters for Linux (perf_events) [1]_ , [2]_ , [3]_
12 direct usage of perf_events system call API [2]_ and over data files
13 generated by Perf tool user mode utility (Perf) [3]_ , [4]_ . The risk
15 units (PMU) [2]_ and Perf collect and expose for performance analysis.
31 (PMC) [8]_ and machine specific registers (MSR) [9]_ that provide
47 security access control management [5]_ .
53 into two categories [6]_ : a) privileged processes (whose effective user
61 based on the process's credentials [5]_ (usually: effective UID,
65 into distinct units, known as capabilities [6]_ , which can be
74 for PTRACE_MODE_READ_REALCREDS ptrace access mode check [7]_ , whose
[all …]
|
| D | tainted-kernels.rst | 56 …git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/tools/debugging/kernel-chktaint>`_
86 1 _/F 2 module was force loaded
87 2 _/S 4 SMP kernel oops on an officially SMP incapable processor
88 3 _/R 8 module was force unloaded
89 4 _/M 16 processor reported a Machine Check Exception (MCE)
90 5 _/B 32 bad page referenced or some unexpected page flags
91 6 _/U 64 taint requested by userspace application
92 7 _/D 128 kernel died recently, i.e. there was an OOPS or BUG
93 8 _/A 256 ACPI table overridden by user
94 9 _/W 512 kernel issued warning
[all …]
|
| D | binderfs.rst | 43 of an `ioctl() <ioctl_>`_.
51 Once the request is made via an `ioctl() <ioctl_>`_ passing a ``struct
55 dynamically.). After the `ioctl() <ioctl_>`_ returns there will be a new
64 Binderfs binder devices can be deleted via `unlink() <unlink_>`_. This means
65 that the `rm() <rm_>`_ tool can be used to delete them. Note that the
|
| /Documentation/process/ |
| D | programming-language.rst | 6 The kernel is written in the C programming language [c-language]_.
7 More precisely, the kernel is typically compiled with ``gcc`` [gcc]_
8 under ``-std=gnu89`` [gcc-c-dialect-options]_: the GNU dialect of ISO C90
11 This dialect contains many extensions to the language [gnu-extensions]_,
14 There is some support for compiling the kernel with ``clang`` [clang]_
15 and ``icc`` [icc]_ for several of the architectures, although at the time
22 [gcc-attribute-syntax]_. Attributes allow to introduce
25 to the language (e.g. adding a new keyword) [n2049]_.
|
| /Documentation/translations/it_IT/process/ |
| D | programming-language.rst | 11 Il kernel è scritto nel linguaggio di programmazione C [c-language]_.
12 Più precisamente, il kernel viene compilato con ``gcc`` [gcc]_ usando
13 l'opzione ``-std=gnu89`` [gcc-c-dialect-options]_: il dialetto GNU
16 Questo dialetto contiene diverse estensioni al linguaggio [gnu-extensions]_,
20 [clang]_ e ``icc`` [icc]_ su diverse architetture, tuttavia in questo momento
27 [gcc-attribute-syntax]_. Gli attributi permettono di aggiungere una semantica,
30 linguaggio stesso (come l'aggiunta di nuove parole chiave) [n2049]_.
|
| /Documentation/media/uapi/cec/ |
| D | cec-ioc-adap-g-log-addrs.rst | 168 * .. _`CEC-LOG-ADDRS-FL-ALLOW-UNREG-FALLBACK`:
176 * .. _`CEC-LOG-ADDRS-FL-ALLOW-RC-PASSTHRU`:
186 * .. _`CEC-LOG-ADDRS-FL-CDC-ONLY`:
205 * .. _`CEC-OP-CEC-VERSION-1-3A`:
210 * .. _`CEC-OP-CEC-VERSION-1-4B`:
215 * .. _`CEC-OP-CEC-VERSION-2-0`:
231 * .. _`CEC-OP-PRIM-DEVTYPE-TV`:
236 * .. _`CEC-OP-PRIM-DEVTYPE-RECORD`:
241 * .. _`CEC-OP-PRIM-DEVTYPE-TUNER`:
246 * .. _`CEC-OP-PRIM-DEVTYPE-PLAYBACK`:
[all …]
|
| D | cec-ioc-g-mode.rst | 88 * .. _`CEC-MODE-NO-INITIATOR`:
94 * .. _`CEC-MODE-INITIATOR`:
101 * .. _`CEC-MODE-EXCL-INITIATOR`:
125 * .. _`CEC-MODE-NO-FOLLOWER`:
130 * .. _`CEC-MODE-FOLLOWER`:
138 * .. _`CEC-MODE-EXCL-FOLLOWER`:
148 * .. _`CEC-MODE-EXCL-FOLLOWER-PASSTHRU`:
161 * .. _`CEC-MODE-MONITOR-PIN`:
175 * .. _`CEC-MODE-MONITOR`:
188 * .. _`CEC-MODE-MONITOR-ALL`:
[all …]
|
| D | cec-ioc-adap-g-caps.rst | 79 * .. _`CEC-CAP-PHYS-ADDR`:
88 * .. _`CEC-CAP-LOG-ADDRS`:
96 * .. _`CEC-CAP-TRANSMIT`:
106 * .. _`CEC-CAP-PASSTHROUGH`:
112 * .. _`CEC-CAP-RC`:
117 * .. _`CEC-CAP-MONITOR-ALL`:
123 * .. _`CEC-CAP-NEEDS-HPD`:
131 * .. _`CEC-CAP-MONITOR-PIN`:
|
| /Documentation/sphinx/ |
| D | parse-headers.pl | 41 $data .= $_;
43 my $ln = $_;
56 if ($is_enum && $ln =~ m/^\s*([_\w][\w\d_]+)\s*[\,=]?/) {
60 $n =~ tr/_/-/;
69 if ($ln =~ m/^\s*#\s*define\s+([_\w][\w\d_]+)\s+_IO/) {
78 if ($ln =~ m/^\s*#\s*define\s+([_\w][\w\d_]+)\s+/) {
82 $n =~ tr/_/-/;
88 if ($ln =~ m/^\s*typedef\s+([_\w][\w\d_]+)\s+(.*)\s+([_\w][\w\d_]+);/) {
95 if ($ln =~ m/^\s*enum\s+([_\w][\w\d_]+)\s+\{/
96 || $ln =~ m/^\s*enum\s+([_\w][\w\d_]+)$/
[all …]
|
| /Documentation/translations/zh_CN/process/ |
| D | license-rules.rst | 49 `许可标识符`_ 一节中进行了解释，并且已可以在
105 的标记中。有关详细信息，请参阅 `许可标识符`_ 一章中的 `例外`_ 。
136 1. _`优先许可`:
143 此目录中的文件包含完整的许可证文本和 `元标记`_ 。文件名与SPDX许可证标识
156 _`元标记`:
173 它们应根据 `许可标识符语法`_ 指南放入源文件中。
215 此目录中的文件包含完整的许可证文本和 `元标记`_ 。文件名与SPDX许可证标识
230 “其他”许可证的元标签要求与 `优先许可`_ 的要求相同。
249 3. _`例外`:
256 此目录中的文件包含完整的例外文本和所需的 `例外元标记`_ 。
[all …]
|
| /Documentation/power/ |
| D | video.rst | 105 Acer TM 660 ??? [#f1]_
112 Asus L2400D s3_mode (3) [#f2]_ (S1 also works OK)
118 Compal CL-50 ??? [#f1]_
125 Dell Inspiron 4000 ??? [#f1]_
126 Dell Inspiron 500m ??? [#f1]_
129 Dell Inspiron 600m ??? [#f1]_
130 Dell Inspiron 8200 ??? [#f1]_
131 Dell Inspiron 8500 ??? [#f1]_
132 Dell Inspiron 8600 ??? [#f1]_
137 HP NX7000 ??? [#f1]_
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 26 LinuxCon Europe 2015 presentation by Kristen Accardi [1]_ for more
29 refer to Intel Software Developer’s Manual [2]_). However, the ``CPUFreq`` core
51 registered (see `below <status_attr_>`_).
122 (see `Energy vs Performance Hints`_ below).
280 used relative to ACPI-based CPU performance scaling (see `below <acpi-cpufreq_>`_
285 ``no_turbo`` attribute in ``sysfs`` (described `below <no_turbo_attr_>`_) should
298 * The maximum supported `non-turbo P-state <turbo_>`_.
302 * The maximum supported `one-core turbo P-state <turbo_>`_ (if turbo P-states
315 list, unless it supports the `HWP feature <Active Mode_>`_. [The interface to
337 P-state <turbo_>`_).
[all …]
|
| /Documentation/ |
| D | digsig.txt | 92 603976250 --alswrv 0 -1 \_ keyring: _uid.0
93 817777377 --alswrv 0 0 \_ user: kmk
94 891974900 --alswrv 0 0 \_ encrypted: evm-key
95 170323636 --alswrv 0 0 \_ keyring: _module
96 548221616 --alswrv 0 0 \_ keyring: _ima
97 128198054 --alswrv 0 0 \_ keyring: _evm
|
| /Documentation/bpf/ |
| D | index.rst | 10 `Documentation/networking/filter.txt`_, which describe both classical
12 The Cilium project also maintains a `BPF and XDP Reference Guide`_
15 The primary info for the bpf syscall is available in the `man-pages`_
16 for `bpf(2)`_.
|
| /Documentation/core-api/ |
| D | gcc-plugins.rst | 10 compiler [1]_. They are useful for runtime instrumentation and static analysis.
12 callbacks [2]_, GIMPLE [3]_, IPA [4]_ and RTL passes [5]_.
25 This infrastructure was ported from grsecurity [6]_ and PaX [7]_.
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-stm32-usbphyc.txt | 9 |_ PLL
11 |_ PHY port#1 _________________ HOST controller
12 | _ |
14 |_ PHY port#2 ----| |________________
16 |_ UTMI switch_______| OTG controller
|
123456789