Home
last modified time | relevance | path

Searched full:probably (Results 1 – 25 of 1708) sorted by relevance

12345678910>>...69

/linux-5.10/Documentation/scheduler/
Dcompletion.rst16 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-5.10/Documentation/cdrom/
Dide-cd.rst17 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
/linux-5.10/include/linux/
Diopoll.h33 * 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
/linux-5.10/Documentation/fb/
Dmatroxfb.rst165 - 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-5.10/net/batman-adv/
Dbitarray.c60 /* 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-5.10/arch/powerpc/
DKconfig.debug116 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
367 working in architecture specific areas of the kernel - probably
/linux-5.10/drivers/leds/
DTODO18 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-5.10/drivers/pci/hotplug/
DTODO30 or ibmphp should store a pointer to its bus in struct slot. Probably the
59 or sgi_hotplug should store a pointer to it in struct slot. Probably the
/linux-5.10/drivers/media/pci/bt8xx/
Dbttv-if.c79 /* 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-5.10/arch/arm/mach-pxa/include/mach/
Dpalmtx.h28 #define GPIO_NR_PALMTX_SD_POWER 114 /* probably */
29 #define GPIO_NR_PALMTX_SD_READONLY 115 /* probably */
/linux-5.10/net/can/
DKconfig28 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-5.10/lib/kunit/
Dtry-catch.c36 * 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()
/linux-5.10/Documentation/admin-guide/pm/
Dstrategies.rst51 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-5.10/drivers/staging/vc04_services/interface/
DTODO22 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
/linux-5.10/tools/testing/selftests/rcutorture/doc/
Drcu-test-image.txt28 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-5.10/Documentation/watchdog/
Dconvert_drivers_to_kernel_api.rst21 Here is a overview of the functions and probably needed actions:
106 Because of the simplifications, a few defines are probably unused now. Remove
121 watchdog_device as a parameter to these functions, so you probably have to
/linux-5.10/Documentation/power/
Dbasic-pm-debugging.rst121 (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-5.10/drivers/net/arcnet/
DKconfig15 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-5.10/arch/um/
DKconfig76 you probably want to say Y here.
190 It is safe to say Y, but you probably don't need this.
/linux-5.10/drivers/staging/mt7621-pinctrl/
DTODO3 - should probably be always selected by 'config RALINK'
/linux-5.10/include/asm-generic/
Dstring.h6 * Architectures probably want to provide at least their own optimized
/linux-5.10/Documentation/hwmon/
Dadm1021.rst56 Prefix: 'max1617' (probably detected as a max1617)
64 Prefix: 'max1617' (probably detected as a max1617)
/linux-5.10/drivers/staging/kpc2000/
DTODO2 - The kpc_i2c driver is a hot mess, it should probably be cleaned up a ton. It functions against c…
/linux-5.10/arch/arm/mach-tango/
Dsmc.S9 dsb /* This barrier is probably unnecessary */
/linux-5.10/drivers/mtd/nand/raw/
Dnand_hynix.c129 * probably tweaked at production in this case). in hynix_nand_setup_read_retry()
437 * happens, this probably means Hynix decided to use in hynix_nand_extract_oobsize()
470 * happens, this probably means Hynix decided to use in hynix_nand_extract_oobsize()
532 * happens, this probably means Hynix decided to use in hynix_nand_extract_ecc_requirements()
559 * happens, this probably means Hynix decided in hynix_nand_extract_ecc_requirements()

12345678910>>...69