| /kernel/linux/linux-6.6/drivers/misc/lkdtm/ |
| D | lkdtm.h | 17 pr_warn("This is probably expected, since this %s was built *without* " #kconfig "=y\n", \
28 …pr_warn("This is probably expected, since this %s was built with " #kconfig "=y but booted with '"…
42 …pr_warn("This is probably expected, as this %s was built *without* " #kconfig "=y and booted with …
50 …pr_err("This is probably expected, since this %s was built *without* " #kconfig "=y (and booted wi…
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/ci/ |
| D | build.yml | 69 # db410c and db820c don't boot with KASAN_INLINE, probably due to the kernel
81 # db410c and db820c don't boot with KASAN_INLINE, probably due to the kernel
93 # db410c and db820c don't boot with KASAN_INLINE, probably due to the kernel
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/st/ |
| D | ste-db9500.dtsi | 23 * This is probably only used if the kernel tries
25 * applications, which the mainline kernel probably
|
| D | ste-db8520.dtsi | 41 * This is probably only used if the kernel tries
43 * applications, which the mainline kernel probably
|
| D | ste-db8500.dtsi | 41 * This is probably only used if the kernel tries
43 * applications, which the mainline kernel probably
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | ste-db9500.dtsi | 24 * This is probably only used if the kernel tries
26 * applications, which the mainline kernel probably
|
| D | ste-db8520.dtsi | 42 * This is probably only used if the kernel tries
44 * applications, which the mainline kernel probably
|
| D | ste-db8500.dtsi | 42 * This is probably only used if the kernel tries
44 * applications, which the mainline kernel probably
|
| /kernel/linux/linux-6.6/Documentation/scheduler/ |
| D | completion.rst | 16 you probably want to look into using one of the wait_for_completion*()
182 most cases you probably don't want to call this with held mutexes.
190 probably want to make a note explaining this (e.g. see
202 interrupted case - which is probably not what you want::
218 If the returned timeout value is deliberately ignored a comment should probably explain
269 probably are a design bug.
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | completion.rst | 16 you probably want to look into using one of the wait_for_completion*()
182 most cases you probably don't want to call this with held mutexes.
190 probably want to make a note explaining this (e.g. see
202 interrupted case - which is probably not what you want::
218 If the returned timeout value is deliberately ignored a comment should probably explain
269 probably are a design bug.
|
| /kernel/linux/linux-5.10/Documentation/cdrom/ |
| D | ide-cd.rst | 17 probably will). This driver will not work with `ATAPI` drives which
92 your system in this manner, you can probably still use the driver.
165 experiencing problems, you should probably also review
170 In most cases, you should probably check with `dmesg` for any errors
199 nonexistent or nonresponding I/O address, you'll probably get
222 probably not making it to the host.
285 If you see a dump, then the drive and driver are probably working
312 probably need a newer version of mount. Early versions would not
321 upgrade, you can probably work around the problem by specifying a
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | iopoll.h | 33 * When available, you'll probably want to use one of the specialized
77 * When available, you'll probably want to use one of the specialized
119 * When available, you'll probably want to use one of the specialized
139 * When available, you'll probably want to use one of the specialized
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | iopoll.h | 33 * When available, you'll probably want to use one of the specialized
81 * When available, you'll probably want to use one of the specialized
131 * When available, you'll probably want to use one of the specialized
151 * When available, you'll probably want to use one of the specialized
|
| /kernel/linux/linux-6.6/drivers/pci/hotplug/ |
| D | TODO | 30 or ibmphp should store a pointer to its bus in struct slot. Probably the
51 or sgi_hotplug should store a pointer to it in struct slot. Probably the
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | matroxfb.rst | 165 - 0 -> 2x128Kx32 chips, 2MB onboard, probably sgram
166 - 1 -> 2x128Kx32 chips, 4MB onboard, probably sgram
167 - 2 -> 2x256Kx32 chips, 4MB onboard, probably sgram
168 - 3 -> 2x256Kx32 chips, 8MB onboard, probably sgram
169 - 4 -> 2x512Kx16 chips, 8/16MB onboard, probably sdram only
171 - 6 -> 4x128Kx32 chips, 4MB onboard, probably sgram
172 - 7 -> 4x128Kx32 chips, 8MB onboard, probably sgram
282 on. Do not forget that if you want sync on green, you also probably
|
| /kernel/linux/linux-6.6/Documentation/fb/ |
| D | matroxfb.rst | 165 - 0 -> 2x128Kx32 chips, 2MB onboard, probably sgram
166 - 1 -> 2x128Kx32 chips, 4MB onboard, probably sgram
167 - 2 -> 2x256Kx32 chips, 4MB onboard, probably sgram
168 - 3 -> 2x256Kx32 chips, 8MB onboard, probably sgram
169 - 4 -> 2x512Kx16 chips, 8/16MB onboard, probably sdram only
171 - 6 -> 4x128Kx32 chips, 4MB onboard, probably sgram
172 - 7 -> 4x128Kx32 chips, 8MB onboard, probably sgram
282 on. Do not forget that if you want sync on green, you also probably
|
| /kernel/linux/linux-6.6/net/batman-adv/ |
| D | bitarray.c | 60 /* sequence number is much newer, probably missed a lot of packets */ in batadv_bit_get_packet()
82 "Other host probably restarted!\n"); in batadv_bit_get_packet()
|
| /kernel/linux/linux-5.10/net/batman-adv/ |
| D | bitarray.c | 60 /* sequence number is much newer, probably missed a lot of packets */ in batadv_bit_get_packet()
82 "Other host probably restarted!\n"); in batadv_bit_get_packet()
|
| /kernel/linux/linux-5.10/arch/powerpc/ |
| D | Kconfig.debug | 116 Include support for disassembling in xmon. You probably want
308 You probably want 0x30000000 for your first serial port and
327 You probably want 0x40000200 for ebony boards and
368 working in architecture specific areas of the kernel - probably
|
| /kernel/linux/linux-5.10/arch/arm/mach-pxa/include/mach/ |
| D | palmtx.h | 28 #define GPIO_NR_PALMTX_SD_POWER 114 /* probably */
29 #define GPIO_NR_PALMTX_SD_READONLY 115 /* probably */
|
| /kernel/linux/linux-5.10/drivers/pci/hotplug/ |
| D | TODO | 30 or ibmphp should store a pointer to its bus in struct slot. Probably the
56 or sgi_hotplug should store a pointer to it in struct slot. Probably the
|
| /kernel/linux/linux-5.10/drivers/media/pci/bt8xx/ |
| D | bttv-if.c | 79 /* prior setting BT848_GPIO_REG_INP is (probably) not needed in bttv_read_gpio()
97 /* prior setting BT848_GPIO_REG_INP is (probably) not needed in bttv_write_gpio()
|
| /kernel/linux/linux-6.6/drivers/leds/ |
| D | TODO | 18 No two LEDs have same name, so the names are probably unusable for the
73 And probably user-friendly interface to access LEDs for particular
|
| /kernel/linux/linux-6.6/net/can/ |
| D | Kconfig | 28 the BSD socket API. You probably want to use the raw socket in
41 You probably want to use the bcm socket in most cases where cyclic
|
| /kernel/linux/linux-6.6/drivers/media/pci/bt8xx/ |
| D | bttv-if.c | 79 /* prior setting BT848_GPIO_REG_INP is (probably) not needed in bttv_read_gpio()
97 /* prior setting BT848_GPIO_REG_INP is (probably) not needed in bttv_write_gpio()
|