Searched full:about (Results 1 – 25 of 1116) sorted by relevance
12345678910>>...45
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 20 device descriptor parameters. The full information about
30 device descriptor parameters. The full information about
41 about the descriptor could be found at UFS specifications 2.1.
51 The full information about the descriptor could be found
62 about the descriptor could be found at UFS specifications 2.1.
72 The full information about the descriptor could be found
83 parameters. The full information about the descriptor could
95 parameters. The full information about the descriptor could
107 about the descriptor could be found at UFS specifications 2.1.
117 about the descriptor could be found at UFS specifications 2.1.
[all …]
|
| D | sysfs-mce | 12 For more details about the x86 machine check architecture
16 For more details about the architecture
90 This option will be useful if you never care about corrected
|
| /Documentation/arch/arm/sunxi/ |
| D | clocks.rst | 2 Frequently asked questions about the sunxi clock system
6 about the sunxi clock system, as well as accompanying ASCII art when adequate.
26 When you are about to suspend, you switch the CPU Mux to the 32kHz
47 Q: Were can I learn more about the sunxi clocks?
|
| /Documentation/process/ |
| D | management-style.rst | 17 Btw, when talking about "kernel manager", it's all about the technical
19 companies. If you sign purchase orders or you have any clue about the
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
165 you can call just about **anybody** a d*ckhead, and you often **will** be
180 scan nearly as well. But I'm sure he thought about it.
198 which is what the game is all about.
202 good idea - go wild", or "That sounds good, but what about xxx?". The
204 new about "xxx" or seem **extra** managerial by pointing out something the
205 smarter person hadn't thought about. In either case, you win.
[all …]
|
| D | handling-regressions.rst | 198 dangerous way to fix a regression. Don't worry about mainlining a fixed
234 * When receiving reports about regressions in recent stable or longterm kernel
281 with the change, but let all involved parties know about the risk. Hence, make
284 list about the risk, so everyone has the change on the radar in case reports
288 What else is there to known about regressions?
311 More about regression tracking and regzbot
342 duty: they need to tell regzbot about the regression report using the ``#regzbot
348 links to the patch description pointing to all reports about the issue fixed.
359 Do I have to tell regzbot about every regression I stumble upon?
365 while. Hence, it's best to tell regzbot about every regression, except when you
[all …]
|
| /Documentation/filesystems/ |
| D | quota.rst | 20 For more details about quota design, see the documentation in quota-tools package
29 Thus quota netlink interface has been designed to pass information about
35 more details about this layer). The name of the quota generic netlink interface
41 This command is used to send a notification about any of the above mentioned
|
| /Documentation/core-api/ |
| D | folio_queue.rst | 14 * Querying information about a folio
15 * Querying information about a folio_queue
98 Querying information about a folio
101 Information about the folio in a particular slot may be queried by the
120 Querying information about a folio_queue
123 Information may be retrieved about a particular segment with the following
138 segment. These are more about indicating how many slots in the array have been
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 5 This document explains the thinking about the revamped and streamlined
17 much stronger than they were before in 2.4 (and people were happy about
54 and we never got a single complaint about nice +19 being too _weak_ in
55 terms of CPU utilization, we only got complaints about it (still) being
63 about Linux's nice level support was its asymmetry around the origin
|
| /Documentation/userspace-api/media/dvb/ |
| D | dvb-fe-read-status.rst | 11 tuner lock status and provide statistics about the quality of the
14 The information about the frontend tuner locking status can be queried
|
| D | fe-get-info.rst | 14 about the - front-end. This call only requires read-only access to the device.
37 obtain information about driver and hardware capabilities. The ioctl
|
| D | fe-read-status.rst | 13 FE_READ_STATUS - Returns status information about the front-end. This call only requires - read-onl…
36 used to check about the locking status of the frontend after being
|
| /Documentation/fb/ |
| D | internals.rst | 5 This is a first start for some documentation about frame buffer device
25 Device independent unchangeable information about a frame buffer device and
31 Device independent changeable information about a frame buffer device and a
46 Generic information, API and low level information about a specific frame
|
| /Documentation/trace/rv/ |
| D | monitor_wwnr.rst | 30 in the processor without being set as RUNNABLE. Think about a
31 task about to sleep::
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | bq24735.yaml | 41 See spec for more information about the ChargeCurrent (0x14h) register.
49 See spec for more information about the ChargeVoltage (0x15h) register.
57 See the spec for more information about the InputCurrent (0x3fh) register.
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-enc-index.rst | 13 VIDIOC_G_ENC_INDEX - Get meta data about a compressed video stream
34 The :ref:`VIDIOC_G_ENC_INDEX <VIDIOC_G_ENC_INDEX>` ioctl provides meta data about a compressed
45 Each element of the ``entry`` array contains meta data about one
79 - Meta data about a compressed video stream. Each element of the
|
| /Documentation/input/ |
| D | uinput.rst | 31 For examples and more information about libevdev:
70 * The ioctls below will enable the device that is about to be
89 * the event, otherwise it will not notice the event we are about
152 * the event, otherwise it will not notice the event we are about
207 * The ioctls below will enable the device that is about to be
223 * the event, otherwise it will not notice the event we are about
|
| /Documentation/scsi/ |
| D | scsi_eh.rst | 154 assumed to forget about the scmd at that point. However, if a scmd
156 about the scmd, which currently no LLDD does, the command is still
161 We'll talk about how SCSI EH takes actions to abort - make LLDD
162 forget about - timed out scmds later.
204 device forget about timed out scmds and make them ready for new
241 timed-out scmds, SCSI EH ensures that LLDD forgets about a scmd
358 all related hardware forget about the scmd.
389 that lower layers have forgotten about the scmd and we can
398 and STU doesn't make lower layers forget about those
453 On completion, the handler should have made lower layers forget about
[all …]
|
| /Documentation/driver-api/media/ |
| D | index.rst | 9 This section contains usage information about media subsystem and
16 - for usage information about media subsystem and supported drivers;
|
| /Documentation/tools/rtla/ |
| D | rtla.rst | 19 precise information about the properties and root causes of unexpected
26 Gives information about the operating system noise (osnoise).
|
| /Documentation/accounting/ |
| D | cgroupstats.rst | 18 Statistics about the state of all the tasks in the cgroup is returned to
22 about tasks blocked on I/O. If CONFIG_TASK_DELAY_ACCT is disabled, this
|
| /Documentation/admin-guide/sysctl/ |
| D | index.rst | 30 this document, and if you come to me complaining about how you
61 several (arch-dependent?) subdirs. Each subdir is mainly about
65 This documentation is about:
87 really like to hear about it :-)
|
| /Documentation/arch/arm/ |
| D | mem_alignment.rst | 22 mode isn't recommended for performance reasons (just think about the
23 floating point emulation that works about the same way). Fix your code
43 slow (think about the floating point emulator) and
|
| /Documentation/netlink/specs/ |
| D | netdev.yaml | 186 for information about individual statistics.
506 doc: Get / dump information about a netdev.
523 doc: Notification about device appearing.
528 doc: Notification about device disappearing.
533 doc: Notification about device configuration being changed.
539 Get / dump information about Page Pools.
560 doc: Notification about page pool appearing.
566 doc: Notification about page pool disappearing.
572 doc: Notification about page pool configuration being changed.
627 doc: Get information about NAPI instances configured on the system.
|
| /Documentation/arch/x86/x86_64/ |
| D | machinecheck.rst | 29 For more details about the x86 machine check architecture
32 For more details about the architecture
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 37 options about how that value is driven, so that for example only one
74 to have different conventions about what "active" means. Such decisions should
77 means "active") so that drivers only need to worry about the logical signal and
78 not about what happens at the line level.
|
12345678910>>...45