| /kernel/linux/linux-4.19/arch/arm/mach-u300/ |
| D | dummyspichip.c | 101 pr_warn("Simple test 3: FAILURE: failed with status %d (probably FIFO overrun)\n", in dummy_looptest()
125 …pr_warn("Simple test 5 step 1: FAILURE: spi_write() failed with status %d (probably FIFO overrun)\… in dummy_looptest()
131 …pr_warn("Simple test 5 step 2: FAILURE: spi_read() failed with status %d (probably FIFO overrun)\n… in dummy_looptest()
141 …pr_warn("Simple test 6 step 1: FAILURE: spi_write() failed with status %d (probably FIFO overrun)\… in dummy_looptest()
147 …pr_warn("Simple test 6 step 2: FAILURE: spi_read() failed with status %d (probably FIFO overrun)\n… in dummy_looptest()
186 pr_warn("Simple test 9: FAILURE: failed with status %d (probably FIFO overrun)\n", in dummy_looptest()
196 …pr_warn("Simple test 10 step 1: FAILURE: spi_write() failed with status %d (probably FIFO overrun)… in dummy_looptest()
203 …pr_warn("Simple test 10 step 2: FAILURE: spi_read() failed with status %d (probably FIFO overrun)\… in dummy_looptest()
|
| /kernel/linux/linux-4.19/Documentation/scheduler/ |
| D | completion.txt | 16 msleep(1) loop to allow something else to proceed, you probably want to
139 time, you probably don't want to call this with held mutexes.
147 probably want to make a note explaining this (e.g. see
156 probably not what you want.
170 deliberately ignored a comment should probably explain why (e.g. see
224 probably are a design bug.
|
| /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-db8500.dtsi | 42 * This is probably only used if the kernel tries
44 * 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
|
| /kernel/linux/linux-4.19/Documentation/cdrom/ |
| D | ide-cd | 15 probably will). This driver will not work with `ATAPI' drives which
90 your system in this manner, you can probably still use the driver.
163 experiencing problems, you should probably also review
168 In most cases, you should probably check with `dmesg' for any errors
197 nonexistent or nonresponding I/O address, you'll probably get
220 probably not making it to the host.
283 If you see a dump, then the drive and driver are probably working
310 probably need a newer version of mount. Early versions would not
319 upgrade, you can probably work around the problem by specifying a
|
| /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
76 * When available, you'll probably want to use one of the specialized
117 * When available, you'll probably want to use one of the specialized
137 * When available, you'll probably want to use one of the specialized
|
| /kernel/linux/linux-4.19/drivers/staging/vc04_services/interface/vchi/ |
| D | TODO | 22 there's a lot code that got built that's probably unnecessary these
45 The driver should probably be using the standard kernel logging mechanisms
|
| /kernel/linux/linux-4.19/Documentation/fb/ |
| D | matroxfb.txt | 151 G200: 0 -> 2x128Kx32 chips, 2MB onboard, probably sgram
152 1 -> 2x128Kx32 chips, 4MB onboard, probably sgram
153 2 -> 2x256Kx32 chips, 4MB onboard, probably sgram
154 3 -> 2x256Kx32 chips, 8MB onboard, probably sgram
155 4 -> 2x512Kx16 chips, 8/16MB onboard, probably sdram only
157 6 -> 4x128Kx32 chips, 4MB onboard, probably sgram
158 7 -> 4x128Kx32 chips, 8MB onboard, probably sgram
261 Do not forget that if you want sync on green, you also probably
|
| /kernel/linux/linux-4.19/net/can/ |
| D | Kconfig | 26 the BSD socket API. You probably want to use the raw socket in
39 You probably want to use the bcm socket in most cases where cyclic
|
| /kernel/linux/linux-4.19/arch/powerpc/ |
| D | Kconfig.debug | 122 Include support for disassembling in xmon. You probably want
306 You probably want 0x30000000 for your first serial port and
325 You probably want 0x40000200 for ebony boards and
365 working in architecture specific areas of the kernel - probably
|
| /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-4.19/Documentation/gpu/ |
| D | todo.rst | 71 helpers (and drivers then moved over to clipped coordinates). Probably the
192 drm_atomic_helper_suspend/resume() can probably be converted to use
211 probably use drm_fb_helper_fbdev_teardown().
330 it shows up. Everything else probably needs to be delayed to some worker or
348 - We probably want to have some support for debugfs files on crtc/connectors and
422 - backlight helpers, probably best to put them into a new drm_backlight.c.
436 - spi helpers, probably best put into spi core/helper code. Thierry said
444 - tinydrm_gem_cma_prime_import_sg_table should probably go into the cma
|
| /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-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-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-4.19/arch/arm/mach-pxa/include/mach/ |
| D | palmtx.h | 32 #define GPIO_NR_PALMTX_SD_POWER 114 /* probably */
33 #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-4.19/tools/testing/selftests/rcutorture/doc/ |
| D | rcu-test-image.txt | 3 probably much better ways of doing this, and this filesystem could no
4 doubt be smaller. It is probably also possible to simply download
|
| /kernel/linux/linux-5.10/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-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-4.19/net/batman-adv/ |
| D | bitarray.c | 72 /* sequence number is much newer, probably missed a lot of packets */ in batadv_bit_get_packet()
94 "Other host probably restarted!\n"); in batadv_bit_get_packet()
|
| /kernel/linux/linux-5.10/lib/kunit/ |
| D | try-catch.c | 36 * TODO(brendanhiggins@google.com): We should probably have some type of in kunit_test_timeout()
46 * one, we probably want to have some sort of test runner level in kunit_test_timeout()
|