/linux/Documentation/ABI/testing/ |
H A 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/net/ax25/ |
H A 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 92 about digital amateur radio in general is on the WWW at 107 users as well as information about how to configure an AX.25 port is 111 about digital amateur radio in general is on the WWW at
|
/linux/Documentation/process/ |
H A 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 …]
|
H A 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 …]
|
H A 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/drivers/clk/ingenic/ |
H A D | cgu.h | 18 * struct ingenic_cgu_pll_info - information about a PLL 71 * struct ingenic_cgu_mux_info - information about a clock mux 84 * struct ingenic_cgu_div_info - information about a divider 113 * struct ingenic_cgu_fixdiv_info - information about a fixed divider 121 * struct ingenic_cgu_gate_info - information about a clock gate 135 * struct ingenic_cgu_custom_info - information about a custom (SoC) clock 143 * struct ingenic_cgu_clk_info - information about a clock 191 * struct ingenic_cgu - data about the CGU 194 * @clock_info: an array containing information about implemented clocks
|
/linux/include/linux/ |
H A D | kmsan.h | 33 * @task: task about to finish. 61 * kmsan_alloc_page() - Notify KMSAN about an alloc_pages() call. 72 * kmsan_free_page() - Notify KMSAN about a free_pages() call. 92 * kmsan_slab_alloc() - Notify KMSAN about a slab allocation. 103 * kmsan_slab_free() - Notify KMSAN about a slab deallocation. 112 * kmsan_kmalloc_large() - Notify KMSAN about a large slab allocation. 122 * kmsan_kfree_large() - Notify KMSAN about a large slab deallocation. 130 * kmsan_map_kernel_range_noflush() - Notify KMSAN about a vmap. 148 * kmsan_vunmap_kernel_range_noflush() - Notify KMSAN about a vunmap. 158 * kmsan_ioremap_page_range() - Notify KMSAN about a ioremap_page_range() call. [all …]
|
/linux/drivers/net/ethernet/chelsio/ |
H A 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/sound/soc/sof/imx/ |
H A 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/sound/soc/sof/mediatek/ |
H A 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/Documentation/core-api/ |
H A 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
|
/linux/Documentation/arch/arm/sunxi/ |
H A 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/drivers/media/dvb-core/ |
H A 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/tools/objtool/arch/loongarch/include/arch/ |
H A D | special.h | 6 * See more info about struct exception_table_entry 14 * See more info about struct jump_entry 23 * See more info about struct alt_instr
|
/linux/Documentation/filesystems/ |
H A 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/tools/perf/pmu-events/arch/powerpc/power10/ |
H A D | others.json | 45 …le through the pipeline using the load gather buffer. This typically adds about 10 cycles to the l… 50 …le through the pipeline using the load gather buffer. This typically adds about 10 cycles to the l… 55 …d require an additional recycle through the pipeline. This typically adds about 10 cycles to the l… 60 …d require an additional recycle through the pipeline. This typically adds about 10 cycles to the l…
|
/linux/Documentation/scheduler/ |
H A 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/drivers/dma-buf/ |
H A 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/dmabuf/buffers`` exposes information about 49 * Detailed documentation about the interface is present in
|
/linux/Documentation/scsi/ |
H A 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 364 that lower layers have forgotten about the scmd and we can 373 and STU doesn't make lower layers forget about those 428 On completion, the handler should have made lower layers forget about 469 lower layers forget about them before doing anything else with [all …]
|
/linux/arch/mips/jazz/ |
H A 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/Documentation/input/ |
H A 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/Documentation/netlink/specs/ |
H A D | netdev.yaml | 186 for information about individual statistics. 526 doc: Get / dump information about a netdev. 543 doc: Notification about device appearing. 548 doc: Notification about device disappearing. 553 doc: Notification about device configuration being changed. 559 Get / dump information about Page Pools. 580 doc: Notification about page pool appearing. 586 doc: Notification about page pool disappearing. 592 doc: Notification about page pool configuration being changed. 647 doc: Get information about NAPI instances configured on the system.
|
/linux/drivers/net/phy/ |
H A D | open_alliance_helpers.h | 11 * information about the cable status and faults. The exact register offset 33 * 000001 = error about 0-1m away 36 * 011111 = error about 30-31m away
|
/linux/drivers/clk/samsung/ |
H A D | clk.h | 18 * struct samsung_clk_provider - information about clock provider 33 * struct samsung_clock_alias - information about mux clock 54 * struct samsung_fixed_rate_clock - information about fixed-rate clock 79 * struct samsung_fixed_factor_clock - information about fixed-factor clock 107 * struct samsung_mux_clock - information about mux clock 157 * struct samsung_div_clock - information about div clock 203 * struct samsung_gate_clock - information about gate clock 249 * struct samsung_pll_clock - information about pll clock
|
/linux/Documentation/admin-guide/ |
H A 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 …]
|