Searched full:do (Results 1 – 25 of 1405) sorted by relevance
12345678910>>...57
| /Documentation/devicetree/bindings/ |
| D | writing-bindings.rst | 17 - DO attempt to make bindings complete even if a driver doesn't support some
24 - DO use node names matching the class of the device. Many standard names are
27 - DO check that the example matches the documentation especially after making
42 - DO make 'compatible' properties specific. DON'T use wildcards in compatible
43 strings. DO use fallback compatibles when devices are the same as or a subset
44 of prior implementations. DO add new compatibles in case there are new
47 - DO use a vendor prefix on device-specific property names. Consider if
54 - DO use common property unit suffixes for properties with scientific units.
58 - DO define properties in terms of constraints. How many entries? What are
69 - For names used in {clock,dma,interrupt,reset}-names, do not add any suffix,
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 43 To reduce its OS jitter, do any of the following:
50 2. Do all eHCA-Infiniband-related work on other CPUs, including
62 To reduce its OS jitter, do the following:
73 To reduce its OS jitter, do one of the following:
93 Do all of the following:
103 do not offline any other CPUs, because doing so could force the
109 Do all of the following:
121 Do all of the following:
133 Do all of the following:
145 Do one or more of the following:
[all …]
|
| /Documentation/netlink/specs/ |
| D | nfsd.yaml | 155 do:
166 do:
178 do:
186 do:
195 do:
203 do:
212 do:
220 do:
|
| D | ethtool.yaml | 1151 do: &strset-get-op
1168 do: &linkinfo-get-op
1187 do:
1200 do: &linkmodes-get-op
1223 do:
1236 do: &linkstate-get-op
1256 do: &debug-get-op
1271 do:
1284 do: &wol-get-op
1300 do:
[all …]
|
| D | nftables.yaml | 1153 do:
1167 do:
1177 do:
1187 do:
1201 do:
1211 do:
1221 do:
1231 do:
1245 do:
1255 do:
[all …]
|
| D | mptcp_pm.yaml | 282 do: &add-addr-attrs
292 do: *add-addr-attrs
298 do: &get-addr-attrs
316 do: *add-addr-attrs
323 do: &mptcp-limits
333 do: &mptcp-get-limits
348 do: &mptcp-set-flags
360 do: &announce-add
371 do:
382 do: &sf-create
[all …]
|
| D | devlink.yaml | 1237 do:
1260 do:
1285 do:
1302 do:
1324 do:
1336 do:
1352 do:
1363 do:
1385 do:
1409 do:
[all …]
|
| /Documentation/tools/rtla/ |
| D | common_hist_options.rst | 11 Do not print header.
15 Do not print summary.
19 Do not print index.
|
| /Documentation/power/ |
| D | opp.rst | 111 Do not use this function in interrupt context.
117 /* Do things */
123 /* Do cpufreq things */
125 /* Do remaining things */
152 /* dont operate on the pointer.. just do a sanity check.. */
190 /* Do stuff like policy checks etc. */
197 /* do something when we can't satisfy the req */
198 /* do other stuff */
211 Do not use these functions in interrupt context.
217 implementation might choose to do something as follows::
[all …]
|
| D | swsusp.rst | 14 If you do resume from initrd after your filesystems are mounted...
22 between suspend and resume, it may do something wrong. If you change
60 should not do that.]
62 If you want to limit the suspend image size to N bytes, do::
138 You bought new UPS for your server. How do you install it without
143 seconds to failure. What do you do? Suspend to disk.
150 We do use the regular I/O paths. However we cannot restore the data
210 "platform" is actually right thing to do where supported, but
214 I do not understand why you have such strong objections to idea of
218 Do selective suspend during runtime power management, that's okay. But
[all …]
|
| /Documentation/sound/cards/ |
| D | audiophile-usb.rst | 41 * Digital Stereo Output (Do)
59 - Ai+Ao+Di+Do
64 - Ai+Ao+Do or Ai+Di+Ao or Ai+Di+Do or Di+Ao+Do
68 - Ai or Ao or Di or Do
73 * The Do port additionally supports surround-encoded AC-3 and DTS passthrough,
76 - Note that in this setup only the Do interface can be enabled
128 * hw:1,1 is Do in playback and Ai in capture
129 * hw:1,2 is Do in AC3/DTS passthrough mode
150 * playing a S16_BE encoded raw file to the Do port::
154 * playing an ac3 sample file to the Do port::
[all …]
|
| /Documentation/process/ |
| D | stable-api-nonsense.rst | 28 You think you want a stable kernel interface, but you really do not, and
42 the world, they neither see this interface, nor do they care about it at
47 that describes kernel drivers that do not have their source code
51 are real, and you do need to be aware of them at all times.)
110 current interfaces, or figure out a better way to do things. If they do
111 that, they then fix the current interfaces to work better. When they do
134 interfaces and do things in improper ways, causing the stability of the
142 to extra work for the USB developers. Since all Linux USB developers do
143 their work on their own time, asking programmers to do extra work for no
163 What to do
[all …]
|
| D | coding-style.rst | 132 we do y
136 while, do). E.g.:
168 ie a ``while`` in a do-statement or an ``else`` in an if-statement, like
173 do {
174 body of do-loop
197 Do not unnecessarily use braces where a single statement will do.
246 if, switch, case, for, do, while
255 Do not add spaces around (inside) parenthesized expressions. This example is
293 Do not leave trailing whitespace at the ends of lines. Some editors with
296 However, some such editors do not remove the whitespace if you end up not
[all …]
|
| D | management-style.rst | 14 to do with reality. It started as a lark, but that doesn't mean that it
18 lead persons, not the people who do traditional management inside
57 needs to do is to turn the big and painful ones into small things where
70 Thus the key to avoiding big decisions becomes to just avoiding to do
112 actually do the work also think twice about whether it's worth doing or
118 Remember: they'd better know more about the details than you do, and
120 thing you can do as a manager is not to instill confidence, but rather a
121 healthy dose of critical thinking on what they do.
124 we just do both?" and look pitiful. Trust me, it works. If it's not
159 The problem with #1 is that it's very easy to do, since you can say
[all …]
|
| D | maintainer-kvm-x86.rst | 9 valued and encouraged. Please do not be discouraged or intimidated by the
52 directly to the main KVM tree, i.e. do not route through the KVM x86 tree.
78 acceptance, i.e. not just for feedback or an update, please do everything you
88 ``git://git.kernel.org/pub/scm/virt/kvm/kvm.git master``. Note, fixes do not
118 Except for a handful of special snowflakes, do not use kernel-doc comments for
127 what it does. Do not reiterate what the code literally does; let the code
137 Do not reference specific sections, tables, figures, etc. by number, especially
142 Generally speaking, do not explicitly reference or copy-paste from the SDM or
162 **DO NOT use x86/kvm!** ``x86/kvm`` is used exclusively for Linux-as-a-KVM-guest
163 changes, i.e. for arch/x86/kernel/kvm.c. Do not use file names or complete file
[all …]
|
| /Documentation/scsi/ |
| D | qlogicfas.rst | 31 thing to do is load the kernel without resetting the hardware, which
59 Make sure it works properly under DOS. You should also do an initial FDISK
71 you can do multiple tests on smaller files. Then do a COMP to verify
73 tests, otherwise you will test your RAM and not the files). Then do
75 realbig.doc realbig.doc". Then do it after the computer gets warm.
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 58 testing services. If you do expose a branch that may be unstable in
61 - Do not rebase a branch that contains history created by others. If you
67 - Do not reparent a tree without a good reason to do so. Just being on a
71 - If you must reparent a repository, do not pick some random kernel commit
109 Subsystem maintainers find themselves having to do two types of merges:
128 branches. Failure to do so threatens the security of the development
162 should do it first.
174 So what should a maintainer do when there is a conflict between their
185 asking upstream to do.
188 resolve dependencies. These dependency issues do happen at times, and
[all …]
|
| /Documentation/userspace-api/netlink/ |
| D | genetlink-legacy.rst | 118 do: ...
121 do: ...
128 do: ...
144 ``reply`` sections of the operations (if an operation has both ``do``
145 and ``dump`` the IDs are shared, ``value`` should be set in ``do``).
154 do:
170 do: ...
283 Multi-message DO
286 New Netlink families should never respond to a DO operation with multiple
289 At the spec level we can define a ``dumps`` property for the ``do``,
|
| /Documentation/hwmon/ |
| D | submitting-patches.rst | 22 * Please use the standard multi-line comment style. Do not mix C and C++
62 through Lindent. Lindent is not perfect, and you may have to do some minor
116 only do it after you have already gathered enough data to be certain that the
129 possible. Do not use any of the deprecated registration functions.
134 * Do not provide support for deprecated sysfs attributes.
136 * Do not create non-standard attributes unless really needed. If you have to use
137 non-standard attributes, or you believe you do, discuss it on the mailing list
143 capabilities. While we do not expect your driver to support everything the
|
| /Documentation/core-api/ |
| D | kref.rst | 38 You must initialize the kref after you allocate it. To do this, call
63 refcount cannot go to zero) you may do this without a lock.
72 holding a valid pointer, it is safe to do this without
93 . do stuff with data here
117 . do stuff with data here
136 do something like::
151 bad style. Don't do it.
156 to do a get then a put::
163 Just do the enqueue. A comment about this is always welcome::
211 The kref_put() return value is useful if you do not want to hold the
[all …]
|
| /Documentation/networking/ |
| D | 6lowpan.rst | 28 Example to evaluate the private usually you can do::
39 /* do great stuff which is ARPHRD_6LOWPAN related */
42 /* do 802.15.4 6LoWPAN handling here */
|
| /Documentation/locking/ |
| D | preempt-locking.rst | 62 means you can't do oddball things like acquire a lock and go off to
63 play while another task releases it. If you want to do something
79 preempt_enable_no_resched() decrement, but do not immediately preempt
88 Note that you do not need to explicitly prevent preemption if you are holding
96 know that the affected codepath does not do any of this. Best policy is to use
142 be made. Do note that calls from interrupt context or bottom half/ tasklets
143 are also protected by preemption locks and so may use the versions which do
|
| /Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 12 do audio/video muxing/encoding/decoding makes it more complex than most.
21 This meant that all drivers had to do the setup of device instances and
23 to do right and many drivers never did do it correctly.
|
| /Documentation/mm/ |
| D | active_mm.rst | 19 and when I do I feel better about more people reading them.
32 user-level page tables at all, so when we do a context switch into an
67 user exited on another CPU while a lazy user was still active, so you do
80 should generally just do
84 instead (which makes more sense anyway - the test is basically one of "do
|
| D | allocation-profiling.rst | 71 do not properly belong to the outer allocation context and should be counted
77 e.g. kmalloc() and do a little more work, then are called in multiple places;
81 To fix up a given helper, for example foo(), do the following:
92 Do this when you're implementing a generic data structure that does allocations
97 To do so:
|
12345678910>>...57