| /linux/arch/riscv/ |
| H A D | Kconfig.errata | 22 If you don't know what to do here, say "Y".
66 If you don't know what to do here, say "Y".
77 If you don't know what to do here, say "Y".
118 If you don't know what to do here, say "Y".
131 If you don't know what to do here, say "Y".
144 If you don't know what to do here, say "Y".
155 If you don't know what to do here, say "Y".
|
| H A D | Kconfig.vendor | 16 If you don't know what to do here, say Y.
29 If you don't know what to do here, say Y.
42 If you don't know what to do here, say Y.
55 If you don't know what to do here, say Y.
68 If you don't know what to do here, say Y.
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | verifier_var_off.c | 26 * &skb->pkt_type, but we don't know which \ in variable_offset_ctx_access()
52 * we don't know which \ in stack_read_priv_vs_unpriv()
75 * we don't know which \ in variable_offset_stack_read_uninitialized()
106 * fp-16, but we don't know which \ in stack_write_priv_vs_unpriv()
119 * were in the range of that write (even if the verifier doesn't actually know if
144 * we don't know which \ in stack_write_followed_by_read()
186 * we don't know which. \ in stack_write_clobbers_spilled_regs()
252 * we don't know which \ in access_max_out_of_bound()
310 * we don't know which \ in access_min_out_of_bound()
339 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know\ in access_min_off_min_initialized()
[all...] |
| /linux/arch/microblaze/ |
| H A D | Kconfig | 134 Unless you know what you are doing, say N here.
162 Say N here unless you know what you are doing.
188 Say N here unless you know what you are doing.
202 Say N here unless you know what you are doing.
216 Say N here unless you know what you are doing.
|
| /linux/drivers/vfio/ |
| H A D | Kconfig | 14 If you don't know what to do here, say N.
28 If you don't know what to do here, say N.
38 If you don't know what to do here, say Y.
76 If you don't know what to do here, say N.
|
| /linux/Documentation/devicetree/bindings/ |
| H A D | common-properties.txt | 15 know the peripheral always needs to be accessed in big endian (BE) mode.
17 unconditionally (e.g. readl/writel). Use this if you know the
71 by all of its devices. The driver needs to know how many devices the
|
| /linux/Documentation/sound/cards/ |
| H A D | bt87x.rst | 34 The driver is now stable. However, it doesn't know about many TV cards,
35 and it refuses to load for cards it doesn't know.
45 or not, so that future versions of this driver know about your card.
|
| /linux/Documentation/power/ |
| H A D | swsusp-dmcrypt.rst | 10 You know how dm-crypt works. If not, visit the following web page:
13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
14 You know how to create or how to modify an initrd.
119 Please don't mind the weird loop above, busybox's msh doesn't know
|
| /linux/Documentation/i2c/ |
| H A D | instantiating-devices.rst | 6 level. Instead, the software must know which devices are connected on each
113 main chip by the means of an I2C bus. You won't know the number of the I2C
138 A variant of this is when you don't know for sure if an I2C device is
232 In general, the kernel should know which I2C devices are connected and
263 device is not officially supported yet but you know it is compatible.
272 available, and you don't need to know what driver the device needs.
|
| /linux/arch/nios2/ |
| H A D | Kconfig | 150 Say N here unless you know what you are doing.
164 Say N here unless you know what you are doing.
176 Say N here unless you know what you are doing.
|
| /linux/sound/soc/bcm/ |
| H A D | Kconfig | 21 If you don't know what to do here, say N.
30 If you don't know what to do here, say N
|
| /linux/Documentation/process/ |
| H A D | management-style.rst | 45 manage had better know the details better than you, so if they come to
49 (Corollary:if the people you manage don't know the details better than
56 makes you look like you know what you're doing, so what a kernel manager
118 Remember: they'd better know more about the details than you do, and
229 Then make the developer who really screwed up (if you can find them) know
231 future, but so that they know they owe you one. And, perhaps even more
|
| /linux/tools/usb/usbip/libsrc/ |
| H A D | list.h | 14 * sometimes we already know the next/prev entries and we can
37 * This is only for internal list manipulation where we know
67 * This is only for internal list manipulation where we know
|
| /linux/arch/openrisc/ |
| H A D | Kconfig | 197 If you don't know what to do here, say N.
206 If you don't know what to do here, say Y.
220 Say N here if you know that your OpenRISC processor has
|
| /linux/Documentation/scsi/ |
| H A D | 53c700.rst | 37 driver, you need to know three things about the way the chip is wired
44 Optionally, you may also need to know other things, like how to read
69 This will be a standard SCSI driver (I don't know of a good document
|
| /linux/drivers/uio/ |
| H A D | Kconfig | 12 If you don't know what to do here, say N.
39 If you don't know what to do here, say N.
56 If you don't know what to do here, say N.
|
| /linux/drivers/vfio/pci/ |
| H A D | Kconfig | 21 If you don't know what to do here, say N.
32 If you don't know what to do here, say N.
|
| /linux/Documentation/fb/ |
| H A D | metronomefb.rst | 30 originally labeled 23P01201_60_WT0107_MTC. I do not know what it stands for.
33 I neither have access to nor know exactly what the waveform does in terms of
|
| /linux/arch/x86/kernel/ |
| H A D | i8253.c | 18 * HPET replaces the PIT, when enabled. So we need to know, which of
29 * requires to know the local APIC timer frequency as it normally is
|
| /linux/drivers/hid/bpf/progs/ |
| H A D | Wacom__ArtPen.bpf.c | 22 * - to solve that, given that we know that the next event will be the same as
61 * we need to know which device has which offsets
80 * the verifier to know we are addressing the memory correctly
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_timeline_types.h | 77 * global_seqno. When we know that all tracked fences are completed
78 * (i.e. when the driver is idle), we know that the syncmap is
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | sysfs.rst | 24 know for example that GPIO #23 controls the write protect line used to
29 and the kernel would have no need to know about it.
33 standard kernels won't know about. And for some tasks, simple userspace
|
| /linux/Documentation/locking/ |
| H A D | spinlocks.rst | 35 sequences that you **know** need to be split up: avoid it at all cost if you
109 cheaper versions of the spinlocks. IFF you know that the spinlocks are
118 This is useful if you know that the data in question is only ever
|
| /linux/drivers/gpu/drm/msm/adreno/ |
| H A D | a6xx_gmu.h | 208 * Let the GMU know that a boot or slumber operation has started. The value in
209 * REG_A6XX_GMU_BOOT_SLUMBER_OPTION lets the GMU know which operation we are
214 * Let the GMU know to not turn off any GPU registers while the CPU is in a
|
| /linux/Documentation/devicetree/bindings/power/supply/ |
| H A D | mediatek,mt6370-charger.yaml | 23 We need to use the IRQ "MT6370_IRQ_OVPCTRL_UVP_D" to know when USB
26 IRQ "MT6370_IRQ_ATTACH" will be triggered, and the driver will know
|