Searched full:probably (Results 1 – 25 of 1954) sorted by relevance
12345678910>>...79
| /linux-6.12.1/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…
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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()
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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()
|
| /linux-6.12.1/Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 134 the hardware probably is malfunctional and damage prevention is requested.
154 the hardware probably is malfunctional and damage prevention is requested
176 the hardware probably is malfunctional and damage prevention is requested
205 the hardware probably is malfunctional and damage prevention is requested
|
| /linux-6.12.1/Documentation/admin-guide/pm/ |
| D | strategies.rst | 51 for example by closing its lid (if the system is a laptop), it probably should
53 away from the laptop keyboard, it probably should stay in the working state and
|
| /linux-6.12.1/drivers/soc/litex/ |
| D | litex_soc_ctrl.c | 48 …panic("Scratch register read error - the system is probably broken! Expected: 0x%x but got: 0x%lx", in litex_check_csr_access()
57 …panic("Scratch register write error - the system is probably broken! Expected: 0x%x but got: 0x%lx… in litex_check_csr_access()
|
| /linux-6.12.1/tools/testing/selftests/rcutorture/doc/ |
| D | rcu-test-image.txt | 28 kernel. There are probably much better ways of doing this, and this
29 filesystem could no doubt be smaller. It is probably also possible to
|
| /linux-6.12.1/lib/kunit/ |
| D | try-catch.c | 40 * TODO(brendanhiggins@google.com): We should probably have some type of in kunit_test_timeout()
50 * one, we probably want to have some sort of test runner level in kunit_test_timeout()
|
| /linux-6.12.1/Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.rst | 21 Here is a overview of the functions and probably needed actions:
105 Because of the simplifications, a few defines are probably unused now. Remove
120 watchdog_device as a parameter to these functions, so you probably have to
|
| /linux-6.12.1/Documentation/power/ |
| D | basic-pm-debugging.rst | 121 (that would probably involve rebooting the system, so always note what drivers
149 the problem is most probably hardware-related and serious, so it should be
163 probably is a problem with a driver statically compiled into the kernel and you
169 unload n/2 of the modules and try again (that would probably involve rebooting
|
| /linux-6.12.1/arch/arm/boot/dts/ti/omap/ |
| D | motorola-mapphone-common.dtsi | 18 /* Poweroff GPIO probably connected to CPCAP */
43 * HDMI 5V regulator probably sourced from battery. Let's keep
57 /* This is probably coming straight from the battery.. */
294 * rts pin probably for PM purposes to PIN_INPUT_PULLUP | MUX_MODE7
|
| /linux-6.12.1/drivers/net/arcnet/ |
| D | Kconfig | 15 chipset of your card. If you don't know, then it's probably a
78 card you had, this is probably the one for you.
|
| /linux-6.12.1/arch/powerpc/ |
| D | Kconfig.debug | 134 Include support for disassembling in xmon. You probably want
324 You probably want 0x30000000 for your first serial port and
343 You probably want 0x40000200 for ebony boards and
|
| /linux-6.12.1/include/asm-generic/ |
| D | string.h | 6 * Architectures probably want to provide at least their own optimized
|
| /linux-6.12.1/Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 144 command should probably be added to the /etc/ppp/cablemodem script
154 You probably have a non-matching kernel source tree and
199 of the SB1000. To do this, it's probably best to download Franco's
|
| /linux-6.12.1/Documentation/networking/ |
| D | eql.rst | 25 It's probably the former. If you find yourself craving more bandwidth,
43 I suggest to ISPs out there that it would probably be fair to charge
111 too far below 296 is probably overkill. Here is an example ifconfig
201 The slave scheduler probably could be replaced with a dozen other
|
12345678910>>...79