Searched full:any (Results 1 – 25 of 1647) sorted by relevance
12345678910>>...66
| /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/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/process/ |
| D | submit-checklist.rst | 27 d) Any Documentation/ changes build successfully without new warnings/errors.
29 fix any issues.
44 6) Any new or modified ``CONFIG`` options do not muck up the config menu and
56 10) Use ``make checkstack`` and fix any problems that it finds.
61 but any one function that uses more than 512 bytes on the stack is a
67 :ref:`kernel-doc <kernel_doc>` and fix any issues.
112 26) If any ioctl's are added by the patch, then also update
115 27) If your modified source code depends on or uses any of the kernel
|
| 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
135 Any member of the committee, including the mediator, can be contacted
144 Any decisions by the committee will be brought to the TAB, for
151 Conduct committee has received and their status, as well details of any
|
| /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
67 being off, and VHE not being disabled by any other means (command line
70 Any other value of r0/x0 triggers a hypervisor-specific handling,
75 clobber any of the caller-saved registers (x0-x18 on arm64, r0-r3 and
|
| /Documentation/admin-guide/ |
| D | security-bugs.rst | 22 As it is with any bug, the more information provided the easier it
25 information is helpful. Any exploit code is very helpful and will not
56 the fix or on any other disclosure channel without the permission of the
58 and followup discussions (if any), exploits, CVE information or the
62 information submitted to the security list and any followup discussions
77 not contribute to actually fixing any potential security problems.
93 to enter any non-disclosure agreements.
|
| /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/networking/ |
| D | driver.rst | 10 any normal circumstances. It is considered a hard error unless
80 must not keep any reference to that SKB and you must not attempt
85 1) Any hardware layer address you obtain for your device should
92 not receive or transmit any data. All in flight packets must
94 any reset commands.
|
| 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/arm/samsung-s3c24xx/ |
| D | suspend.rst | 24 4) Any peripherals that are going to be powered down at the same
37 use for any other purposes (for example, the EB2410ITX uses this to
92 care should be taken that any external clock sources that the UARTs
95 3) If any debugging is placed in the resume path, then it must have the
118 suspend to see if there has been any corruption of the contents.
131 identify any faults with better precision
|
| D | cpufreq.rst | 25 The code core manages the CPU specific drivers, any data that they
28 and anything else associated with it. Any board that wants to use this
63 board requires and any restrictions being placed on it.
66 timings changing, any maximum frequency limits and information about the
|
| /Documentation/RCU/ |
| D | rcu.rst | 10 must be long enough that any readers accessing the item being deleted have
23 not acquire any locks, perform any atomic instructions, write to
24 shared memory, or (on CPUs other than Alpha) execute any memory
35 Therefore, as soon as a CPU is seen passing through any of these
36 three states, we know that that CPU has exited any previous RCU
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | ov772x.txt | 4 such as VGA, QVGA, and any size scaling down from CIF to 40x30. It also can
15 active low, if any.
17 active high, if any.
|
| /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/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/driver-api/serial/ |
| D | driver.rst | 7 driver. It is not complete, any questions you have should be directed to
20 responsible for handling interrupts for the port, and providing any
54 The low level driver is free to use this lock to provide any additional
212 Grab any interrupt resources and initialise any low level driver
223 Disable the port, disable any break condition that may be in
224 effect, and free any interrupt resources. It should not disable
238 Flush any write buffers, reset any DMA state and stop any
319 Perform any power management related activities on the specified
323 This function should not be used to grab any resources.
343 Release any memory and IO region resources currently in use by
[all …]
|
| /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 …]
|
12345678910>>...66