Searched full:probably (Results 1 – 25 of 224) sorted by relevance
123456789
| /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.
|
| /Documentation/w1/masters/ |
| D | mxc-w1.rst | 7 * Freescale MX27, MX31 and probably other i.MX SoCs
|
| /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
|
| /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
|
| /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
|
| D | sa1100fb.rst | 30 will probably be necessary.
|
| /Documentation/scsi/ |
| D | sym53c500_cs.rst | 27 for Tom Corner, and it works for me. Your mileage will probably vary.
|
| D | wd719x.rst | 12 probably cannot be added to linux-firmware.
|
| /Documentation/arch/powerpc/ |
| D | elfnote.rst | 29 being run on a machine with ultravisor, the kernel will probably crash
|
| /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
|
| /Documentation/core-api/ |
| D | boot-time-mm.rst | 17 may be directed to the first (and probably the only) node or to a
|
| /Documentation/usb/ |
| D | dwc3.rst | 41 We probably have to pay attention not to process events once we
|
| /Documentation/driver-api/media/drivers/ |
| D | rkisp1.rst | 24 V20 on the other hand will probably be used in future SoCs and
|
| D | saa7134-devel.rst | 24 - saa7133/35 - saa7135 is probably a marketing decision, since all those
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-ehci_hcd | 44 correct for 2.6.35 (and probably several earlier kernel
|
| /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
|
| /Documentation/devicetree/bindings/clock/ |
| D | marvell,armada-3700-uart-clock.yaml | 28 used for UART (most probably xtal) for smooth boot log on UART.
|
| /Documentation/misc-devices/ |
| D | ad525x_dpot.rst | 31 Locate the device in your sysfs tree. This is probably easiest by going into
|
| /Documentation/ |
| D | subsystem-apis.rst | 10 as needed (or at least as we managed to add it — probably *not* all that is
|
| /Documentation/driver-api/fpga/ |
| D | intro.rst | 14 should go without saying. If that seems necessary, there's probably
|
| /Documentation/bpf/ |
| D | map_bloom_filter.rst | 75 if ``value`` is probably present in the map, or ``-ENOENT`` if ``value``
103 probably present in the map, or ``-ENOENT`` if ``value`` is definitely
|
| /Documentation/filesystems/nfs/ |
| D | reexport.rst | 91 something that also supports NFSv3, you're *probably* OK. Re-exporting
92 over NFSv3 may be dicier, and reexporting over NFSv2 will probably
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | atmel,sama5d4-wdt.yaml | 53 if the CPU stop working while it is in idle state, which is probably
|
| /Documentation/userspace-api/gpio/ |
| D | error-codes.rst | 37 - There was a failure while copying data from/to userspace, probably
|
| /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
|
123456789