Searched full:about (Results 1 – 25 of 4602) sorted by relevance
12345678910>>...185
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/net/ax25/ |
| D | Kconfig | 12 and more specifically about AX.25 on Linux
17 the questions about amateur radio.
39 Information about where to get supporting software for Linux amateur
40 radio as well as information about how to configure an AX.25 port is
44 kernel source. More information about digital amateur radio in
63 be enabled at runtime. For more about DAMA see
88 users as well as information about how to configure an AX.25 port is
91 file <file:Documentation/networking/ax25.rst>. More information about
107 users as well as information about how to configure an AX.25 port is
110 file <file:Documentation/networking/ax25.rst>. More information about
|
| /Linux-v6.1/include/linux/ |
| D | kmsan.h | 33 * @task: task about to finish.
60 * kmsan_alloc_page() - Notify KMSAN about an alloc_pages() call.
71 * kmsan_free_page() - Notify KMSAN about a free_pages() call.
91 * kmsan_slab_alloc() - Notify KMSAN about a slab allocation.
102 * kmsan_slab_free() - Notify KMSAN about a slab deallocation.
111 * kmsan_kmalloc_large() - Notify KMSAN about a large slab allocation.
121 * kmsan_kfree_large() - Notify KMSAN about a large slab deallocation.
129 * kmsan_map_kernel_range_noflush() - Notify KMSAN about a vmap.
144 * kmsan_vunmap_kernel_range_noflush() - Notify KMSAN about a vunmap.
154 * kmsan_ioremap_page_range() - Notify KMSAN about a ioremap_page_range() call.
[all …]
|
| /Linux-v6.1/Documentation/process/ |
| D | handling-regressions.rst | 190 soon or already was stamped "End-of-Life" (EOL) -- this usually happens about
230 with the change, but let all involved parties know about the risk. Hence, make
233 list about the risk, so everyone has the change on the radar in case reports
237 What else is there to known about regressions?
260 More about regression tracking and regzbot
291 duty: they need to tell regzbot about the regression report using the ``#regzbot
297 "Link:" tags to the patch description pointing to all reports about the issue
309 Do I have to tell regzbot about every regression I stumble upon?
315 while. Hence, it's best to tell regzbot about every regression, except when you
339 use regzbot to track severe issues, like reports about hangs, corrupted data,
[all …]
|
| 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 | 1.Intro.rst | 27 :ref:`development_coding` is about the coding process; several pitfalls which
32 :ref:`development_posting` talks about the process of posting patches for
50 What this document is about
96 who will not listen or who do not care about the development process.
183 thinking about doing so), you clearly have an interest in the continued
197 license (about which more will be said below). Your author is not a
215 - Everything that was said above about code review applies doubly to
262 Questions about copyright-related issues are common on Linux development
|
| /Linux-v6.1/drivers/clk/ingenic/ |
| D | cgu.h | 18 * struct ingenic_cgu_pll_info - information about a PLL
64 * struct ingenic_cgu_mux_info - information about a clock mux
77 * struct ingenic_cgu_div_info - information about a divider
106 * struct ingenic_cgu_fixdiv_info - information about a fixed divider
114 * struct ingenic_cgu_gate_info - information about a clock gate
128 * struct ingenic_cgu_custom_info - information about a custom (SoC) clock
136 * struct ingenic_cgu_clk_info - information about a clock
184 * struct ingenic_cgu - data about the CGU
187 * @clock_info: an array containing information about implemented clocks
|
| /Linux-v6.1/drivers/net/ethernet/chelsio/ |
| D | Kconfig | 15 the questions about Chelsio devices. If you say Y, you will be asked for
27 Ethernet cards. More information about adapter features and
31 For general information about Chelsio and our products, visit
58 For general information about Chelsio and our products, visit
81 For general information about Chelsio and our products, visit
122 For general information about Chelsio and our products, visit
|
| /Linux-v6.1/sound/soc/sof/mediatek/ |
| D | mtk-adsp-common.c | 21 * in order to gather information about the registers, filename and
24 * @xoops: Stores information about registers.
25 * @panic_info: Stores information about filename and line number.
67 /* Get information about the panic status from the debug box area. in mtk_adsp_dump()
72 /* Get information about the registers, the filename and line in mtk_adsp_dump()
|
| /Linux-v6.1/sound/soc/sof/imx/ |
| D | imx-common.c | 15 * in order to gather information about the registers, filename and
18 * @xoops: Stores information about registers.
19 * @panic_info: Stores information about filename and line number.
60 /* Get information about the panic status from the debug box area. in imx8_dump()
65 /* Get information about the registers, the filename and line in imx8_dump()
|
| /Linux-v6.1/Documentation/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?
|
| /Linux-v6.1/drivers/media/dvb-core/ |
| D | Kconfig | 43 If you are unsure about this, use the default value 16
56 If you are unsure about this, say N here.
68 If you are unsure about this, say N here.
80 If you are unsure about this, say N here.
|
| /Linux-v6.1/Documentation/scsi/ |
| D | scsi_eh.rst | 151 assumed to forget about the scmd at that point. However, if a scmd
153 about the scmd, which currently no LLDD does, the command is still
158 We'll talk about how SCSI EH takes actions to abort - make LLDD
159 forget about - timed out scmds later.
201 device forget about timed out scmds and make them ready for new
238 timed-out scmds, SCSI EH ensures that LLDD forgets about a scmd
355 all related hardware forget about the scmd.
386 that lower layers have forgotten about the scmd and we can
395 and STU doesn't make lower layers forget about those
450 On completion, the handler should have made lower layers forget about
[all …]
|
| /Linux-v6.1/drivers/net/wireless/intersil/hostap/ |
| D | Kconfig | 20 See <http://hostap.epitest.fi/> for more information about the
65 driver and its help text includes more information about the Host AP
78 driver and its help text includes more information about the Host AP
91 driver and its help text includes more information about the Host AP
|
| /Linux-v6.1/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
|
| /Linux-v6.1/arch/mips/jazz/ |
| D | Kconfig | 8 kernel that runs on these, say Y here. For details about Linux on
19 kernel that runs on these, say Y here. For details about Linux on
29 kernel that runs on these, say Y here. For details about Linux on
|
| /Linux-v6.1/drivers/dma-buf/ |
| D | dma-buf-sysfs-stats.c | 28 * information about DMA-BUF fds. Detailed documentation about the interface
32 * about the DMA-BUFs for which processes hold fds or have the buffers mmapped
36 * The interface at ``/sys/kernel/dma-buf/buffers`` exposes information about
49 * Detailed documentation about the interface is present in
|
| /Linux-v6.1/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
|
| /Linux-v6.1/drivers/clk/samsung/ |
| D | clk.h | 17 * struct samsung_clk_provider: information about clock provider
31 * struct samsung_clock_alias: information about mux clock
52 * struct samsung_fixed_rate_clock: information about fixed-rate clock
77 * struct samsung_fixed_factor_clock: information about fixed-factor clock
105 * struct samsung_mux_clock: information about mux clock
149 * struct samsung_div_clock: information about div clock
192 * struct samsung_gate_clock: information about gate clock
238 * struct samsung_pll_clock: information about pll clock
|
| /Linux-v6.1/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
|
| /Linux-v6.1/fs/sysv/ |
| D | Kconfig | 29 nothing whatsoever to do with the option "System V IPC". Read about
32 Saying Y here will enlarge your kernel by about 27 KB.
37 If you haven't heard about all of this before, it's safe to say N.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/fs/proc/ |
| D | Kconfig | 6 This is a virtual file system providing information about the status
13 information about what the different IRQs are used for at the moment
18 information about your system gathered from the /proc file system.
29 This option will enlarge your kernel by about 67 KB. Several
|
| /Linux-v6.1/usr/ |
| D | Kconfig | 150 is slowest among the choices. The initramfs size is about 10% smaller
165 slowest. The initramfs size is about 33% smaller with LZMA in
176 problems on memory constrained systems. The initramfs size is about
189 kernel size is about 10% bigger than gzip. Despite that, it's
201 size is about 15% bigger than gzip; however its decompression speed
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | reporting-issues.rst | 23 expect to be told about problems, which most of the time will be by email with a
81 need special handling in some steps that are about to follow.
135 that hear about it for the first time. And if you learned something in this
136 process, consider searching again for existing reports about the issue.
144 * Start to compile the report by writing a detailed description about the
172 the point about regression within a stable or longterm kernel version line. You
179 line you care about: go to the `front page of kernel.org
308 developers in fact are willing to handle reports about issues occurring with
313 Sid or Fedora Rawhide. Some developers will also accept reports about issues
360 In case you find an existing report about your issue, join the discussion, as
[all …]
|
12345678910>>...185
