| /kernel/linux/linux-4.19/fs/nls/ |
| D | Kconfig | 44 in so-called DOS codepages. You need to include the appropriate
56 in so-called DOS codepages. You need to include the appropriate
68 in so-called DOS codepages. You need to include the appropriate
81 so-called DOS codepages. You need to include the appropriate
97 so-called DOS codepages. You need to include the appropriate
112 so-called DOS codepages. You need to include the appropriate
123 so-called DOS codepages. You need to include the appropriate
134 so-called DOS codepages. You need to include the appropriate
145 so-called DOS codepages. You need to include the appropriate
156 so-called DOS codepages. You need to include the appropriate
[all …]
|
| /kernel/linux/linux-5.10/fs/nls/ |
| D | Kconfig | 45 in so-called DOS codepages. You need to include the appropriate
57 in so-called DOS codepages. You need to include the appropriate
69 in so-called DOS codepages. You need to include the appropriate
82 so-called DOS codepages. You need to include the appropriate
98 so-called DOS codepages. You need to include the appropriate
113 so-called DOS codepages. You need to include the appropriate
124 so-called DOS codepages. You need to include the appropriate
135 so-called DOS codepages. You need to include the appropriate
146 so-called DOS codepages. You need to include the appropriate
157 so-called DOS codepages. You need to include the appropriate
[all …]
|
| /kernel/linux/linux-4.19/arch/mips/sgi-ip27/ |
| D | TODO | 1 1. Need to figure out why PCI writes to the IOC3 hang, and if it is okay
3 2. Need to figure out RRB allocation in bridge_startup().
4 3. Need to figure out why address swaizzling is needed in inw/outw for
6 4. Need to integrate ip27-klconfig.c:find_lboard and
14 10. Need a bad pmd table, bad pte table. __bad_pmd_table/__bad_pagetable
17 This might need to change later. Only the timer intr is set up to be
|
| /kernel/linux/linux-5.10/arch/mips/sgi-ip27/ |
| D | TODO | 1 1. Need to figure out why PCI writes to the IOC3 hang, and if it is okay
3 2. Need to figure out RRB allocation in bridge_startup().
4 3. Need to figure out why address swaizzling is needed in inw/outw for
6 4. Need to integrate ip27-klconfig.c:find_lboard and
14 10. Need a bad pmd table, bad pte table. __bad_pmd_table/__bad_pagetable
17 This might need to change later. Only the timer intr is set up to be
|
| /kernel/linux/linux-5.10/kernel/sched/ |
| D | core_ctl.c | 318 * To find out how many tasks need higher capacity CPUs.
403 int need = 0; in prev_cluster_nr_need_assist() local
421 need += nr_stats[cpu].nr; in prev_cluster_nr_need_assist()
423 need += compute_prev_cluster_misfit_need(index); in prev_cluster_nr_need_assist()
425 if (need > prev_cluster->active_cpus) in prev_cluster_nr_need_assist()
426 need = need - prev_cluster->active_cpus; in prev_cluster_nr_need_assist()
428 need = 0; in prev_cluster_nr_need_assist()
430 return need; in prev_cluster_nr_need_assist()
518 unsigned int need) in adjustment_possible() argument
520 return (need < cluster->active_cpus || (need > cluster->active_cpus && in adjustment_possible()
[all …]
|
| /kernel/linux/linux-4.19/crypto/ |
| D | crypto_engine.c | 26 * @req: the request need to be finalized
133 /* Until here we get the request need to be encrypted successfully */ in crypto_pump_requests()
184 * @req: the request need to be listed into the engine queue
213 * @req: the request need to be listed into the engine queue
225 * @req: the request need to be listed into the engine queue
239 * @req: the request need to be listed into the engine queue
252 * @req: the request need to be listed into the engine queue
265 * @req: the request need to be listed into the engine queue
278 * @req: the request need to be listed into the engine queue
291 * @req: the request need to be finalized
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | idr.rst | 31 If you need to change the pointer associated with an ID, you can call
37 Some users need to allocate IDs larger than ``INT_MAX``. So far all of
39 idr_alloc_u32(). If you need IDs that will not fit in a u32,
42 If you need to allocate IDs sequentially, you can use
48 iterator-style idr_for_each_entry(). You may need to use
60 If you need to take a lock while allocating a new ID from the IDR,
61 you may need to pass a restrictive set of GFP flags, which can lead
|
| /kernel/linux/linux-4.19/arch/um/drivers/ |
| D | Kconfig | 172 Slip Transport. You'll need at least one of them, but may choose
173 more than one without conflict. If you don't need UML networking,
210 conflict. If you don't need UML networking, say N.
220 To use this form of networking, you'll need to run the UML
229 say Y. If you need a network between UMLs on multiple physical
232 transports. You'll need at least one of them, but may choose
233 more than one without conflict. If you don't need UML networking,
259 To use this form of networking, you will need to run vde_switch
266 If you need UML networking with VDE,
277 bridge if any of them need to be able to talk to their hosts or any
[all …]
|
| /kernel/linux/linux-4.19/drivers/usb/atm/ |
| D | Kconfig | 12 modem to your computer's USB port. You will then need to choose your
25 modem. In order to use your modem you will need to install the
37 AccessRunner chipset. In order to use your modem you will need to
49 or eagle chipset. In order to use your modem you will need to
60 another USB DSL drivers. In order to use your modem you will need to
62 and reception as module parameters. You may need to initialize
|
| /kernel/linux/linux-5.10/drivers/usb/atm/ |
| D | Kconfig | 12 modem to your computer's USB port. You will then need to choose your
25 modem. In order to use your modem you will need to install the
37 AccessRunner chipset. In order to use your modem you will need to
49 or eagle chipset. In order to use your modem you will need to
60 another USB DSL drivers. In order to use your modem you will need to
62 and reception as module parameters. You may need to initialize
|
| /kernel/linux/linux-4.19/Documentation/core-api/ |
| D | idr.rst | 31 If you need to change the pointer associated with an ID, you can call
37 Some users need to allocate IDs larger than ``INT_MAX``. So far all of
39 :c:func:`idr_alloc_u32`. If you need IDs that will not fit in a u32,
42 If you need to allocate IDs sequentially, you can use
48 iterator-style :c:func:`idr_for_each_entry`. You may need to use
60 If you need to take a lock while allocating a new ID from the IDR,
61 you may need to pass a restrictive set of GFP flags, which can lead
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/sound/ |
| D | sirf-audio.txt | 9 - hp-pa-gpios: Need to be present if the board need control external
11 - spk-pa-gpios: Need to be present if the board need control external
13 - hp-switch-gpios: Need to be present if the board capable to detect jack
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | sirf-audio.txt | 9 - hp-pa-gpios: Need to be present if the board need control external
11 - spk-pa-gpios: Need to be present if the board need control external
13 - hp-switch-gpios: Need to be present if the board capable to detect jack
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | journalling.rst | 10 The journalling layer is easy to use. You need to first of all create a
20 Once you have got your journal_t object you need to 'mount' or load the
25 does not need to be processed (or even need not have valid contents), it
38 You still need to actually journal your filesystem changes, this is done
39 by wrapping them into transactions. Additionally you also need to wrap
52 Inside each transaction you need to wrap the modifications to the
54 need to call jbd2_journal_get_create_access() /
60 buffer, and once you are have done so you need to call
100 strategy. Why? Because, if you do a delete, you need to ensure you
116 that need processing when the transaction commits.
[all …]
|
| /kernel/linux/linux-4.19/mm/ |
| D | page_ext.c | 31 * is the need callback which is mandatory if user wants to avoid useless
35 * The need callback is used to decide whether extended memory allocation is
38 * allocating huge chunk of memory, each clients represent their need of
39 * extra memory through the need callback. If one of the need callbacks
42 * none of need callbacks return true, memory isn't needed at all in this boot
46 * When need callback returns true, page_ext checks if there is a request for
80 bool need = false; in invoke_need_callbacks() local
83 if (page_ext_ops[i]->need && page_ext_ops[i]->need()) { in invoke_need_callbacks()
87 need = true; in invoke_need_callbacks()
91 return need; in invoke_need_callbacks()
[all …]
|
| /kernel/linux/linux-5.10/mm/ |
| D | page_ext.c | 31 * is the need callback which is mandatory if user wants to avoid useless
35 * The need callback is used to decide whether extended memory allocation is
38 * allocating huge chunk of memory, each clients represent their need of
39 * extra memory through the need callback. If one of the need callbacks
42 * none of need callbacks return true, memory isn't needed at all in this boot
46 * When need callback returns true, page_ext checks if there is a request for
78 bool need = false; in invoke_need_callbacks() local
81 if (page_ext_ops[i]->need && page_ext_ops[i]->need()) { in invoke_need_callbacks()
84 need = true; in invoke_need_callbacks()
88 return need; in invoke_need_callbacks()
[all …]
|
| /kernel/linux/linux-5.10/crypto/ |
| D | crypto_engine.c | 22 * @req: the request need to be finalized
126 * We'll need it on completion (crypto_finalize_request). in crypto_pump_requests()
141 /* Until here we get the request need to be encrypted successfully */ in crypto_pump_requests()
254 * @req: the request need to be listed into the engine queue
283 * @req: the request need to be listed into the engine queue
295 * @req: the request need to be listed into the engine queue
308 * @req: the request need to be listed into the engine queue
321 * @req: the request need to be listed into the engine queue
334 * @req: the request need to be listed into the engine queue
347 * @req: the request need to be finalized
[all …]
|
| /kernel/linux/linux-4.19/scripts/coccinelle/api/ |
| D | platform_no_drv_owner.cocci | 126 msg = "No need to set .owner here. The core will do it."
133 msg = "No need to set .owner here. The core will do it."
140 msg = "No need to set .owner here. The core will do it."
147 msg = "No need to set .owner here. The core will do it."
156 msg = "No need to set .owner here. The core will do it."
163 msg = "No need to set .owner here. The core will do it."
170 msg = "No need to set .owner here. The core will do it."
177 msg = "No need to set .owner here. The core will do it."
|
| /kernel/linux/linux-5.10/drivers/parport/ |
| D | Kconfig | 23 machines) etc., then you need to say Y here; please read
73 will need to know which IRQ the parallel port has. By default,
90 Say Y here if you need PCMCIA support for your PC-style parallel
98 Say Y here if you need support for the parallel port on
107 Say Y here if you need support for the parallel port hardware on
116 Say Y here if you need parallel port support for the MFC3 card.
125 Say Y here if you need support for the parallel port hardware on
147 Say Y here if you need support for the parallel port hardware on
|
| /kernel/linux/linux-4.19/drivers/parport/ |
| D | Kconfig | 22 machines) etc., then you need to say Y here; please read
72 will need to know which IRQ the parallel port has. By default,
89 Say Y here if you need PCMCIA support for your PC-style parallel
97 Say Y here if you need support for the parallel port on
106 Say Y here if you need support for the parallel port hardware on
115 Say Y here if you need parallel port support for the MFC3 card.
124 Say Y here if you need support for the parallel port hardware on
146 Say Y here if you need support for the parallel port hardware on
|
| /kernel/linux/linux-5.10/scripts/coccinelle/api/ |
| D | platform_no_drv_owner.cocci | 127 msg = "No need to set .owner here. The core will do it."
134 msg = "No need to set .owner here. The core will do it."
141 msg = "No need to set .owner here. The core will do it."
148 msg = "No need to set .owner here. The core will do it."
157 msg = "No need to set .owner here. The core will do it."
164 msg = "No need to set .owner here. The core will do it."
171 msg = "No need to set .owner here. The core will do it."
178 msg = "No need to set .owner here. The core will do it."
|
| /kernel/linux/linux-5.10/drivers/media/v4l2-core/ |
| D | Kconfig | 43 # Used by drivers that need tuner.ko
47 # Used by drivers that need v4l2-jpeg.ko
51 # Used by drivers that need v4l2-h264.ko
55 # Used by drivers that need v4l2-mem2mem.ko
74 # Used by drivers that need Videobuf modules
|
| /kernel/linux/linux-4.19/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.txt | 135 need to ensure application level data integrity is maintained.
163 changes to the log buffers, we need to ensure that the object we are formatting
192 Hence we avoid the need to lock items when we need to flush outstanding
222 The memory buffer and associated vector need to be passed as a single object,
223 but still need to be associated with the parent object so if the object is
230 are in the item, so we'd need a new encapsulation method for regions in the log
236 Hence we need to keep the vector, but by attaching the memory buffer to it and
247 them to be used without limitations, we need to be able to track and accumulate
284 We need to write these items in the order that they exist in the CIL, and they
285 need to be written as an atomic transaction. The need for all the objects to be
[all …]
|
| /kernel/linux/linux-5.10/fs/xfs/ |
| D | xfs_log_cil.c | 25 * we don't want to be issuing transactions from, so we need to tell the
30 * the space required, we need to set the current reservation of the ticket to
52 * tail of the log are. We need this log initialisation done before we can
90 * the CIL and we need a CIL commit to occur to free memory.
92 * To avoid this, we need to move the memory allocation outside the
145 * Ordered items need to be tracked but we do not wish to write in xlog_cil_alloc_shadow_bufs()
146 * them. We need a logvec to track the object, but we do not in xlog_cil_alloc_shadow_bufs()
147 * need an iovec or buffer to be allocated for copying data. in xlog_cil_alloc_shadow_bufs()
157 * of the next one is naturally aligned. We'll need to in xlog_cil_alloc_shadow_bufs()
173 * if we have no shadow buffer, or it is too small, we need to in xlog_cil_alloc_shadow_bufs()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/usb/ |
| D | typec_bus.rst | 11 every alternate mode, so every alternate mode will need a custom driver.
31 needed from the port drivers, but the port drivers need to provide the operation
33 drivers need to provide them for the partner alternate mode devices.
52 in need to reconfigure the pins on the connector, the alternate mode driver
57 chain to notify the external drivers about the state of the connector that need
86 The drivers for the components that the alternate modes are designed for need to
89 example, the GPU drivers will need to know those details. In case of
90 Thunderbolt alternate mode, the thunderbolt drivers will need to know them, and
|