| /Linux-v5.10/tools/testing/selftests/bpf/verifier/ |
| D | var_off.c | 9 * &skb->pkt_type, but we don't know which
31 * we don't know which
81 * we don't know which
106 * we don't know which
130 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know
155 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know
181 /* Add it to fp. We now have either fp-12 or fp-16, we don't know
210 /* Add it to fp. We now have either fp-12 or fp-16, we don't know
235 /* Add it to fp. We now have either fp-12 or fp-16, we don't know
|
| /Linux-v5.10/drivers/vfio/platform/reset/ |
| D | Kconfig | 8 If you don't know what to do here, say N.
16 If you don't know what to do here, say N.
25 If you don't know what to do here, say N.
|
| /Linux-v5.10/arch/microblaze/ |
| D | Kconfig | 141 Unless you know what you are doing, say N here.
178 Say N here unless you know what you are doing.
204 Say N here unless you know what you are doing.
219 Say N here unless you know what you are doing.
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | hpfs.rst | 95 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
105 chgrp symlinks but I don't know what is it good for. chmoding symlink results
110 extended attributes and partly in OS2SYS.INI. I don't want (and don't know how)
146 should work. If you have OS/2 server, use only read-only mode. I don't know how
148 list, I don't know how to delete them when file is deleted and how to not
180 reasons. If you extremely wish to update them, let me know, I'll write it (but
187 anybody know what does it mean?
201 whole created by this driver, it is BUG - let me know about it.
259 1.93 Modified, so that it works with kernels >= 2.1.131, I don't know if it
|
| /Linux-v5.10/Documentation/i2c/ |
| D | instantiating-devices.rst | 6 level. Instead, the software must know which devices are connected on each
109 main chip by the means of an I2C bus. You won't know the number of the I2C
132 A variant of this is when you don't know for sure if an I2C device is
224 In general, the kernel should know which I2C devices are connected and
255 device is not officially supported yet but you know it is compatible.
264 available, and you don't need to know what driver the device needs.
|
| /Linux-v5.10/Documentation/devicetree/bindings/ |
| 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-v5.10/Documentation/sound/cards/ |
| 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-v5.10/arch/powerpc/ |
| D | Kconfig | 451 Select this if you know there does have a hardware FPU on your
588 setting can still be useful to bootwrappers that need to know the
773 Say N unless you know what you are doing.
793 want. Only change this if you know what you are doing.
806 Say N here unless you know what you are doing.
1002 Say Y unless you know what you are doing and the filter is causing
1109 Unless you know what you are doing, say N here.
1124 Say N here unless you know what you are doing.
1140 Say N here unless you know what you are doing.
1173 Say N here unless you know what you are doing.
[all …]
|
| /Linux-v5.10/drivers/vfio/platform/ |
| D | Kconfig | 11 If you don't know what to do here, say N.
21 If you don't know what to do here, say N.
|
| /Linux-v5.10/Documentation/power/ |
| 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-v5.10/Documentation/core-api/ |
| D | dma-attributes.rst | 87 - You know that the accesses to this memory won't thrash the TLB.
88 You might know that the accesses are likely to be sequential or
92 - You know that the penalty of TLB misses while accessing the
96 - You know that the DMA mapping is fairly transitory. If you expect
|
| /Linux-v5.10/sound/soc/bcm/ |
| D | Kconfig | 19 If you don't know what to do here, say N.
28 If you don't know what to do here, say N
|
| /Linux-v5.10/arch/nios2/ |
| D | Kconfig | 156 Say N here unless you know what you are doing.
170 Say N here unless you know what you are doing.
182 Say N here unless you know what you are doing.
|
| /Linux-v5.10/Documentation/staging/ |
| D | xz.rst | 99 decompression code. I don't know if it could have any use in the
100 kernel, but I know that it would be useful in some embedded projects
109 it is good to know this if testing the code e.g. with the test files
121 kernel-related mailing lists, so if there's something I should know,
|
| /Linux-v5.10/drivers/auxdisplay/ |
| D | Kconfig | 61 If you don't know what I'm talking about, load the parport module,
80 If you don't know what I'm talking about, ignore it.
129 If you don't know what I'm talking about, ignore it.
285 If you don't know, put '40' here.
298 If you don't know what your LCD uses, in doubt let 16 here for a 2x16, and
315 If you don't know, use the normal one (0).
324 port. But before assigning signals, the driver needs to know if it will
|
| /Linux-v5.10/drivers/ide/ |
| D | cy82c693.c | 27 * If you know a better value or how to calc it, please let me know.
75 * If you know the correct (best) value for this register please in cy82c693_set_dma_mode()
76 * let me know - ASK in cy82c693_set_dma_mode()
|
| /Linux-v5.10/arch/openrisc/mm/ |
| D | ioremap.c | 35 * caller shouldn't need to know that small detail.
87 /* This is a bit broken... we don't really know in iounmap()
88 * how big the area is so it's difficult to know in iounmap()
|
| /Linux-v5.10/drivers/vfio/ |
| D | Kconfig | 30 If you don't know what to do here, say N.
45 If you don't know what to do here, say N.
|
| /Linux-v5.10/drivers/vfio/pci/ |
| D | Kconfig | 11 If you don't know what to do here, say N.
21 If you don't know what to do here, say N.
|
| /Linux-v5.10/tools/usb/usbip/libsrc/ |
| 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-v5.10/Documentation/process/ |
| 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-v5.10/arch/x86/kernel/ |
| D | i8253.c | 17 * HPET replaces the PIT, when enabled. So we need to know, which of
28 * requires to know the local APIC timer frequency as it normally is
|
| /Linux-v5.10/Documentation/fb/ |
| 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-v5.10/fs/nfsd/ |
| D | lockd.c | 41 /* We return nlm error codes as nlm doesn't know in nlm_fopen()
42 * about nfsd, but nfsd does know about nlm.. in nlm_fopen()
|
| /Linux-v5.10/Documentation/scsi/ |
| 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
|
