| /Documentation/ABI/testing/ |
| D | debugfs-scmi-raw | 9 Any subsequently received response can be read from this same
14 Users: Debugging, any userspace test suite
24 Any subsequently received response can be read from this same
26 Any additional delayed response received afterwards can be read
32 Users: Debugging, any userspace test suite
38 Description: SCMI Raw message errors facility; any kind of timed-out or
43 Users: Debugging, any userspace test suite
49 Description: SCMI Raw notification snooping facility; any notification
54 Users: Debugging, any userspace test suite
61 causes the internal queues of any kind of received message,
[all …]
|
| D | debugfs-scmi | 9 Users: Debugging, any userspace test suite
16 on this SCMI instance <n>, the threshold above which any SCMI
20 Users: Debugging, any userspace test suite
28 Users: Debugging, any userspace test suite
36 Users: Debugging, any userspace test suite
44 Users: Debugging, any userspace test suite
52 Users: Debugging, any userspace test suite
61 Users: Debugging, any userspace test suite
70 Users: Debugging, any userspace test suite
|
| D | debugfs-tpmi | 10 Users: Debugging, any user space test suite
18 Users: Debugging, any user space test suite
25 Allows to write at any offset. It doesn't check for Read/Write access
31 Users: Debugging, any user space test suite
|
| /Documentation/admin-guide/media/ |
| D | zoran-cardlist.rst | 19 - <any>
23 - <any>
31 - <any>
39 - <any>
51 - <any>
|
| /Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 11 examples for any other kernel drivers you want to author, refer to
14 For any kind of mass produced system you want to support, such as servers,
15 laptops, phones, tablets, routers, and any consumer or office or business goods
28 to any existing kernel subsystem and not be a good fit for an operating system,
36 Do not under any circumstances abuse the GPIO userspace ABI to cut corners in
37 any product development projects. If you use it for prototyping, then do not
39 any circumstances deploy any uniform products using GPIO from userspace.
|
| /Documentation/admin-guide/sysctl/ |
| D | user.rst | 41 The maximum number of cgroup namespaces that any user in the current
47 The maximum number of ipc namespaces that any user in the current
53 The maximum number of mount namespaces that any user in the current
59 The maximum number of network namespaces that any user in the
65 The maximum number of pid namespaces that any user in the current
71 The maximum number of time namespaces that any user in the current
77 The maximum number of user namespaces that any user in the current
83 The maximum number of user namespaces that any user in the current
|
| /Documentation/scsi/ |
| D | LICENSE.FlashPoint | 11 Foundation; either version 2, or (at your option) any later version,
18 WITHOUT ANY WARRANTY, without even the implied warranty of MERCHANTABILITY
50 THIS SOFTWARE IS PROVIDED BY MYLEX CORP. ``AS IS'' AND ANY EXPRESS OR
53 NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
57 CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
58 LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
| /Documentation/process/ |
| D | cve.rst | 37 any bug might be exploitable to compromise the security of the kernel,
40 assign CVE numbers to any bugfix that they identify. This
44 If the CVE assignment team misses a specific fix that any user feels
61 No CVEs will be assigned for any issue found in a version of the kernel
75 its appropriate CVE designation. Any attempt to modify or dispute a CVE
89 Any CVE that is assigned against the Linux kernel for an actively
90 supported kernel version, by any group other than the kernel assignment
100 the applicability of any specific CVE is up to the user of Linux to
102 contact us to attempt to determine the applicability of any specific
105 Also, as the source tree is so large, and any one system only uses a
[all …]
|
| D | code-of-conduct-interpretation.rst | 7 provide a set of rules for almost any open source community. Every
53 uncertain about approaching the TAB or any other maintainers, please
92 defined in the MAINTAINERS file in the kernel source tree. Any emails
99 email address, or "official" social media address. Any activity
101 Conduct as published for kernel.org, just as any individual using a
116 bug, though; such bugs will be fixed more quickly if any interested
125 Committee. The exact members receiving these emails at any given time
137 Any member of the committee, including the mediator, can be contacted
146 Any decisions regarding enforcement recommendations will be brought to
153 Conduct committee has received and their status, as well details of any
[all …]
|
| D | submit-checklist.rst | 31 1) Any new or modified ``CONFIG`` options do not muck up the config menu and
59 6) If any ioctl's are added by the patch, then also update
72 3) Use ``make checkstack`` and fix any problems that it finds.
74 but any one function that uses more than 512 bytes on the stack is a
89 d) Any Documentation/ changes build successfully without new warnings/errors.
91 fix any issues.
102 4) If your modified source code depends on or uses any of the kernel
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 6 "fsl,mpc8349-pmc" should be listed for any chip whose PMC is
7 compatible. "fsl,mpc8313-pmc" should also be listed for any chip
10 "fsl,mpc8548-pmc" should be listed for any chip whose PMC is
11 compatible. "fsl,mpc8536-pmc" should also be listed for any chip
14 "fsl,mpc8641d-pmc" should be listed for any chip whose PMC is
41 supports disabling and resuming devices at any time.
|
| /Documentation/livepatch/ |
| D | system-state.rst | 9 Each new livepatch completely replaces any older one. It can keep,
10 add, and even remove fixes. And it is typically safe to replace any version
11 of the livepatch with any other one thanks to the atomic replace feature.
16 any new livepatch must be able to detect what changes have already been
71 - Any completely new system state modification is allowed.
102 - Remove any already made changes when error occurs and the livepatch
118 - Do any other preparatory action that is needed by
156 - Remove any not longer needed setting or data.
162 Therefore it does not need to care about any previously installed
|
| D | cumulative-patches.rst | 8 from any newer livepatch must be done on top of the older ones.
67 A good practice is to set .replace flag in any released livepatch.
78 executed. Any callbacks from the replaced patches are ignored.
80 In other words, the cumulative patch is responsible for doing any actions
81 that are necessary to properly replace any older patch.
91 In any case, it would be a nightmare to think about the order of
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 15 are any methods from the list:
26 which may not sleep and must be callable from any context.
39 are therefore safe to call from any context.
46 the midlayer is also safe to call from any context.
57 The IB midlayer does not perform any serialization of function calls.
60 consumers are not required to perform any serialization. However,
107 ib_unregister_device() from process context. It must not hold any
|
| /Documentation/userspace-api/media/ |
| D | fdl-appendix.rst | 32 used for any textual work, regardless of subject matter or whether it is
45 This License applies to any manual or other work that contains a notice
47 terms of this License. The "Document", below, refers to any such manual
48 or work. Any member of the public is a licensee, and is addressed as
54 A "Modified Version" of the Document means any work containing the
67 may not explain any mathematics.) The relationship could be a matter of
117 do not have any title page as such, "Title Page" means the text near the
127 You may copy and distribute the :ref:`Document <fdl-document>` in any
181 :ref:`Document <fdl-document>` well before redistributing any large
202 if any) a title distinct from that of the
[all …]
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.rst | 10 hypervisor when running as a guest (under Xen, KVM or any other
11 hypervisor), or any hypervisor-specific interaction when the kernel is
28 Unless specified otherwise, any built-in hypervisor must implement
69 any other means (command line option, for example).
71 Any other value of r0/x0 triggers a hypervisor-specific handling,
76 clobber any of the caller-saved registers (x0-x18 on arm64, r0-r3 and
|
| /Documentation/block/ |
| D | pr.rst | 27 device. Any initiator can read from the device.
35 Any initiator can read from the device.
43 Any initiator can read from the device.
85 and thus removes any access restriction implied by it.
100 any outstanding command sent over a connection identified by old_key.
105 This ioctl command unregisters both key and any other reservation key
106 registered with the device and drops any existing reservation.
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | san.rst | 18 relays the dGPU events to any other driver interested via its public API and
26 receiving dGPU events does not miss any events due to the SAN interface not
30 Notifier-blocks can be registered by any device for as long as the module is
32 with |san_dgpu_notifier_register|. If the notifier is not needed any more, it
|
| /Documentation/RCU/ |
| D | rcu.rst | 10 must be long enough that any readers accessing the item being deleted have
22 not acquire any locks, perform any atomic instructions, write to
23 shared memory, or (on CPUs other than Alpha) execute any memory
34 Therefore, as soon as a CPU is seen passing through any of these
35 three states, we know that that CPU has exited any previous RCU
|
| /Documentation/filesystems/ |
| D | autofs.rst | 20 a remote database and can change at any time. The content
35 required with any user-space program. Subsequent text refers to this
84 which are provided by the Linux VFS. Any directory provided by a
92 (potentially) a mount trap. Any access to this directory beyond a
120 Firstly, before checking to see if any filesystem is mounted on the
128 autofs normally returns zero, but first waits for any
132 - A return value of `-EISDIR` tells the VFS to ignore any mounts
155 - Any other negative value is treated as an error and returned
164 - or any other error sent down by the automount daemon.
182 would be safe to follow down into any mounted directory and the only
[all …]
|
| /Documentation/networking/ |
| D | tc-actions-env-rules.rst | 8 The "environmental" rules for authors of any new tc actions are:
10 1) If you stealeth or borroweth any packet thou shalt be branching
17 2) If you munge any packet thou shalt call pskb_expand_head in the case
|
| /Documentation/usb/ |
| D | usb-serial.rst | 53 For any questions or problems with this driver, please contact
71 pressed BEFORE trying to get any program to communicate to the device.
77 (this is usually /dev/ttyUSB1 if you do not have any other usb-serial
98 For any questions or problems with this driver, please contact Greg
150 For any questions or problems with the driver, please contact Ganesh
182 For any questions or problems with this driver, please contact Brian
207 For any questions or problems with this driver, please contact Hugh
221 For any questions or problems with this driver, please contact Bill Ryder.
284 If you have any questions, problems, patches, feature requests, etc. you can
352 For any questions or problems with this driver, please contact William
[all …]
|
| /Documentation/sound/soc/ |
| D | machine.rst | 24 /* the pre and post PM functions are used to do any PM work before and
25 * after the codec and DAIs do any PM work. */
42 probe/remove are optional. Do any machine specific probe here.
48 of any machine audio tasks that have to be done before or after the codec, DAIs
55 also be used to set up the DAI system clock and for any machine related DAI
|
| /Documentation/input/ |
| D | userio.rst | 19 of them. userio accomplishes this by allowing any privileged userspace program
28 kernel module by writing to the device, and any data received from the serio
43 ``type`` describes the type of command that is being sent. This can be any one
50 to the kernel log. Only one command can be sent at a time, any additional data
69 set. Can be any of the macros from <linux/serio.h>. For example: SERIO_8042
|
| /Documentation/dev-tools/kunit/ |
| D | faq.rst | 16 code under test is small and does not have any external dependencies outside of
23 disqualifying any of them from being considered unit testing frameworks.
31 can compile to any architecture. It compiles like just another part of the
52 if the code under test is small and does not have any external dependencies
90 It also preserves any config changes you might make, so you can
94 may help clean up any residual config items which could be causing problems.
96 built into any kernel, or can be built as a module and loaded at runtime.
103 If none of the above tricks help, you are always welcome to email any issues to
|