Searched full:maybe (Results 1 – 25 of 86) sorted by relevance
1234
| /Documentation/driver-api/ |
| D | io_ordering.rst | 39 CPU A: (void)readl(safe_register); /* maybe a config register? */
46 CPU B: (void)readl(safe_register); /* maybe a config register? */
|
| /Documentation/admin-guide/aoe/ |
| D | status.sh | 22 # maybe ls comes up empty, so we use "end"
|
| /Documentation/admin-guide/sysctl/ |
| D | sunrpc.rst | 19 maybe a few other things as well.
|
| /Documentation/hwmon/ |
| D | w83l785ts.rst | 41 and cause read errors. Or maybe the W83L785TS-S chip is simply unreliable,
|
| D | asb100.rst | 32 controller will simply not work (or maybe it will for you... it doesn't for
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 14 some cases, such as re-initializing (and maybe resetting). After such
66 than allowed. This usually indicates some device (maybe the
|
| D | ten-bit-addresses.rst | 32 listed above could stay for a long time, maybe even forever if nobody
|
| /Documentation/admin-guide/media/ |
| D | cx88.rst | 45 1) Try upgrading to the latest snapshot, maybe it has been added
|
| /Documentation/filesystems/ |
| D | locking.rst | 39 d_revalidate: no no yes (ref-walk) maybe
41 d_hash no no no maybe
42 d_compare: yes no no maybe
50 d_manage: no no yes (ref-walk) maybe
198 statfs: maybe(read) (see below)
281 dirty_folio: maybe
431 fl_release_private: maybe maybe[1]_
658 huge_fault: maybe-read
659 map_pages: maybe-read
|
| /Documentation/devicetree/bindings/display/sprd/ |
| D | sprd,display-subsystem.yaml | 19 For different display scenarios, dpu0 and dpu1 maybe binding to different
|
| /Documentation/devicetree/bindings/display/rockchip/ |
| D | rockchip,lvds.yaml | 68 The remote endpoint maybe vopb or vopl.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | sprd,pinctrl.txt | 17 as one generic configuration, and maybe it will add more strange
|
| /Documentation/sphinx/ |
| D | automarkup.py | 286 # validity. (Maybe we can do something in the future to warn about
313 # This loop could eventually be improved on. Someday maybe we
|
| /Documentation/process/ |
| D | handling-regressions.rst | 277 proposed change; if problems surface, maybe some solution acceptable for all
503 avoid them. Maybe we can't practically support the hardware any more
505 more. Maybe there's a serious security issue with how we did things,
506 and people actually depended on that fundamentally broken model. Maybe
512 Behavioral changes happen, and maybe we don't even support some
652 Maybe it worked *because* the user had taken the bug into account,
653 maybe it worked because the user didn't notice - again, it doesn't
|
| D | security-bugs.rst | 91 sense to Cc: both lists at once, except maybe for coordination if and
|
| D | deprecated.rst | 178 itself is important. Maybe it should be removed entirely?
182 up to Linus's scrutiny, maybe you can use "%px", along with making sure
|
| /Documentation/devicetree/bindings/phy/ |
| D | realtek,usb2phy.yaml | 105 For a different board or port, the original magnitude maybe not meet
|
| /Documentation/power/ |
| D | video.rst | 20 using vbetool later, or maybe nothing is necessary on particular
85 your video card (good luck getting docs :-(). Maybe suspending from X
|
| /Documentation/RCU/ |
| D | lockdep-splat.rst | 75 And maybe that lock really does protect this reference. If so, the fix
|
| /Documentation/scsi/ |
| D | libsas.rst | 98 address from the IDENTIFY frame or maybe generate a SAS
142 - I haven't found use for that -- maybe other
|
| /Documentation/spi/ |
| D | spi-summary.rst | 219 maybe coupling it with code to initialize pin configurations, so that
327 onto a card that's maybe just thirty square centimeters. On such systems,
398 (two pointers, maybe the same one in both cases) and half
489 number (maybe the same as the platform device ID) and three methods used to
|
| /Documentation/arch/arm/ |
| D | interrupts.rst | 52 the various operations (maybe this'll change to a better name).
|
| /Documentation/fb/ |
| D | matroxfb.rst | 320 - maybe more...
338 them (maybe that chip overheats, but it has a very big cooler (G100 has
348 - maybe more...
|
| D | framebuffer.rst | 88 If you try to change that information, the driver maybe will round up some
95 it to the hardware (round it down to less bits, maybe throw away
|
| /Documentation/admin-guide/ |
| D | rtc.rst | 134 example, maybe the low-power battery-backed RTC is a discrete I2C chip, but
|
1234