Home
last modified time | relevance | path

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

12345678910>>...55

/linux/drivers/misc/lkdtm/
H A Dlkdtm.h17 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/arch/arm/boot/dts/st/
H A Dste-db9500.dtsi23 * This is probably only used if the kernel tries
25 * applications, which the mainline kernel probably
H A Dste-db8500.dtsi41 * This is probably only used if the kernel tries
43 * applications, which the mainline kernel probably
H A Dste-db8520.dtsi41 * This is probably only used if the kernel tries
43 * applications, which the mainline kernel probably
/linux/Documentation/scheduler/
H A 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/Documentation/fb/
H A Dmatroxfb.rst162 - 0 -> 2x128Kx32 chips, 2MB onboard, probably sgram
163 - 1 -> 2x128Kx32 chips, 4MB onboard, probably sgram
164 - 2 -> 2x256Kx32 chips, 4MB onboard, probably sgram
165 - 3 -> 2x256Kx32 chips, 8MB onboard, probably sgram
166 - 4 -> 2x512Kx16 chips, 8/16MB onboard, probably sdram only
168 - 6 -> 4x128Kx32 chips, 4MB onboard, probably sgram
169 - 7 -> 4x128Kx32 chips, 8MB onboard, probably sgram
279 on. Do not forget that if you want sync on green, you also probably
/linux/net/batman-adv/
H A 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/drivers/media/pci/bt8xx/
H A 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/drivers/leds/
H A 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/net/can/
H A 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/Documentation/admin-guide/pm/
H A 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/tools/testing/selftests/rcutorture/doc/
H A 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/arch/arm/boot/dts/ti/omap/
H A Dmotorola-mapphone-common.dtsi18 /* 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/Documentation/power/
H A 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/Documentation/watchdog/
H A Dconvert_drivers_to_kernel_api.rst21 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/drivers/net/arcnet/
H A 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/Documentation/networking/
H A Deql.rst25 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
/linux/include/asm-generic/
H A Dstring.h6 * Architectures probably want to provide at least their own optimized
/linux/Documentation/bpf/
H A Dmap_bloom_filter.rst75 if ``value`` is probably present in the map, or ``-ENOENT`` if ``value``
103 probably present in the map, or ``-ENOENT`` if ``value`` is definitely
/linux/arch/hexagon/include/asm/
H A Dexec.h11 /* Should probably shoot for an 8-byte aligned stack pointer */
/linux/drivers/siox/
H A DKconfig10 Unless you know better, it is probably safe to say "no" here.
/linux/tools/perf/scripts/python/bin/
H A Dintel-pt-events-record9 echo "and for power events it probably needs to be system wide i.e. -a option"
/linux/kernel/trace/rv/monitors/sleep/
H A DKconfig21 TRACE_IRQFLAGS). Therefore, you probably should say N for
/linux/arch/m68k/hp300/
H A DREADME.hp3009 The serial console is probably broken at the moment but the Topcat/HIL keyboard
/linux/sound/aoa/soundbus/i2sbus/
H A Dinterface.h144 /* probably gives external frequency? */
153 /* frame count reg isn't clear to me yet, but probably useful */

12345678910>>...55