Searched full:sometimes (Results 1 – 25 of 2062) sorted by relevance
12345678910>>...83
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | intro.rst | 56 input de-glitch/debounce logic, sometimes with software controls.
59 sometimes level triggered. Such IRQs may be configurable as system
94 Sometimes shared signals need to use "open drain" (where only the low signal
98 This is sometimes called a "wire-AND"; or more practically, from the negative
102 Also, bidirectional data bus signals sometimes use open drain signals.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | intro.rst | 56 input de-glitch/debounce logic, sometimes with software controls.
59 sometimes level triggered. Such IRQs may be configurable as system
94 Sometimes shared signals need to use "open drain" (where only the low signal
98 This is sometimes called a "wire-AND"; or more practically, from the negative
102 Also, bidirectional data bus signals sometimes use open drain signals.
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | hpfs.rst | 109 moved ... sometimes it works. But the link is partly stored in directory
159 Sometimes you won't be able to delete some files on a very full filesystem
193 Old versions of this driver created sometimes unbalanced dnode trees. OS/2
194 chkdsk doesn't scream if the tree is unbalanced (and sometimes creates
210 Sometimes (I think it's random) when you create a file with one-char name under
283 Fixed a bug with i_blocks (du sometimes didn't display correct values)
294 error sometimes when opening directories in PMSHELL)
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | hpfs.rst | 109 moved ... sometimes it works. But the link is partly stored in directory
159 Sometimes you won't be able to delete some files on a very full filesystem
193 Old versions of this driver created sometimes unbalanced dnode trees. OS/2
194 chkdsk doesn't scream if the tree is unbalanced (and sometimes creates
210 Sometimes (I think it's random) when you create a file with one-char name under
283 Fixed a bug with i_blocks (du sometimes didn't display correct values)
294 error sometimes when opening directories in PMSHELL)
|
| /kernel/linux/linux-5.10/Documentation/sound/soc/ |
| D | clocking.rst | 12 Every audio subsystem is driven by a master clock (sometimes referred to as MCLK
29 clock is sometimes referred to as LRC (left right clock) or FRAME. This clock
|
| /kernel/linux/linux-6.6/Documentation/sound/soc/ |
| D | clocking.rst | 12 Every audio subsystem is driven by a master clock (sometimes referred to as MCLK
29 clock is sometimes referred to as LRC (left right clock) or FRAME. This clock
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/ |
| D | arm,vexpress-juno.yaml | 139 the connection between the motherboard and any tiles. Sometimes the
140 compatible is placed directly under this node, sometimes it is placed
141 in a subnode named "motherboard-bus". Sometimes the compatible includes
142 "arm,vexpress,v2?-p1" sometimes (on software models) is is just
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | arm,vexpress-juno.yaml | 155 the connection between the motherboard and any tiles. Sometimes the
156 compatible is placed directly under this node, sometimes it is placed
157 in a subnode named "motherboard". Sometimes the compatible includes
158 "arm,vexpress,v2?-p1" sometimes (on software models) is is just
|
| /kernel/linux/linux-6.6/tools/memory-model/scripts/ |
| D | judgelitmus.sh | 11 # the Always/Sometimes/Never portion of the "Result:" prediction will be
16 # "HW" is the --hw argument. In addition, non-Sometimes verification
141 if test \( -n "$LKMM_HW_MAP_FILE" -a "$outcome" = Sometimes \) -o -n "$datarace_modeled"
|
| D | checkghlitmus.sh | 39 xargs -r grep -E -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' |
45 xargs < $T/list-C -r grep -E -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' > $T/list-C-result
|
| D | cmplitmushist.sh | 87 echo Matching Observation Always/Sometimes/Never result: $2
116 echo Matching Observation Always/Sometimes/Never result: $obsresult 1>&2
|
| /kernel/linux/linux-5.10/tools/memory-model/scripts/ |
| D | cmplitmushist.sh | 50 echo Matching Observation Always/Sometimes/Never result: $2
79 echo Matching Observation Always/Sometimes/Never result: $obsresult 1>&2
|
| D | checkghlitmus.sh | 38 xargs -r egrep -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' |
44 xargs < $T/list-C -r egrep -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' > $T/list-C-result
|
| /kernel/linux/linux-5.10/drivers/acpi/x86/ |
| D | utils.c | 25 * Likewise sometimes some not-actually present devices are sometimes
96 * drivers sometimes cause crashes under Windows and this is how the
|
| /kernel/linux/linux-5.10/Documentation/i2c/busses/ |
| D | i2c-viapro.rst | 7 Datasheet: Sometimes available at the VIA website
10 Datasheet: Sometimes available at the VIA website
|
| /kernel/linux/linux-6.6/Documentation/i2c/busses/ |
| D | i2c-viapro.rst | 7 Datasheet: Sometimes available at the VIA website
10 Datasheet: Sometimes available at the VIA website
|
| /kernel/linux/linux-5.10/Documentation/ide/ |
| D | ChangeLog.ide-tape.1995-2002 | 84 * user backup program. On my tape drive, it sometimes
117 * now sometimes be used with IDE tape drives as well.
135 * MTTELL was sometimes returning incorrect results.
202 * Also, sometimes an application finishes but the
|
| /kernel/linux/linux-6.6/Documentation/rust/ |
| D | coding-guidelines.rst | 38 individual files, and does not require a kernel configuration. Sometimes it may
67 sometimes it is useful to use both comments and documentation at the same time.
170 While sometimes the reason might look trivial and therefore unneeded,
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | hwlat_detector.rst | 19 management of thermal sensors and fans. Sometimes though, SMIs are used for
21 handler (sometimes measured in milliseconds). Obviously this is a problem if
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | reporting-issues.rst | 238 should be enough for most people. But sometimes there are situations where even
307 Note, the previous paragraph is starting with the word 'most', as sometimes
324 better than not reporting the issue at all: sometimes such reports directly or
416 Problems that look a lot like a kernel issue are sometimes caused by build or
450 Reminder, you are dealing with computers, which sometimes do unexpected things,
520 the issue afterwards. Sometimes simply restarting will be enough, sometimes
529 they are Open Source): they sometimes cause errors in unrelated kernel
652 name is too specific. Sometimes you will need to search on the net for help;
671 that was replaced by a newer solution you need to switch to. Sometimes the code
728 areas rarely changed (like old or unmaintained drivers): sometimes such code is
[all …]
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| D | hwlat_detector.rst | 19 management of thermal sensors and fans. Sometimes though, SMIs are used for
21 handler (sometimes measured in milliseconds). Obviously this is a problem if
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/ci/xfails/ |
| D | msm-sc7180-flakes.txt | 4 # sometimes.. tbd if this is a kernel CRC bug or a test
|
| D | msm-sdm845-flakes.txt | 5 # sometimes.. tbd if this is a kernel CRC bug or a test
|
| /kernel/linux/linux-6.6/Documentation/driver-api/driver-model/ |
| D | overview.rst | 20 (sometimes just a list) for the devices they control. There wasn't any
43 and sometimes by the device-specific drivers.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
| D | overview.rst | 20 (sometimes just a list) for the devices they control. There wasn't any
43 and sometimes by the device-specific drivers.
|
12345678910>>...83