Searched full:past (Results 1 – 25 of 98) sorted by relevance
1234
| /Documentation/userspace-api/media/dvb/ |
| D | examples.rst | 9 In the past, we used to have a set of examples here. However, those
|
| D | dvbproperty.rst | 16 In the past (up to DVB API version 3 - DVBv3), the strategy used was to have a
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-gate.yaml | 15 some kind of operation to access the i2c bus past the arbitrator/gate, but
|
| /Documentation/filesystems/ext4/ |
| D | verity.rst | 40 Verity files cannot have blocks allocated past the end of the verity
|
| D | group_descr.rst | 96 - Lower 16-bits of unused inode count. If set, we needn't scan past the
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-controller.yaml | 41 there is a need to "step past" a mux controller and set some other idle
100 there is a need to "step past" a mux controller and set some other idle
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 29 from the queue that was generated some time in the past.
|
| /Documentation/fb/ |
| D | pvr2fb.rst | 61 XF86_FBDev has been shown to work on the Dreamcast in the past - though not yet
|
| /Documentation/admin-guide/thermal/ |
| D | intel_powerclamp.rst | 127 cannot be based on the past or current input. Therefore, the
135 past samples and outputs are included in the feedback. For example, a
138 derivative gains of the past samples.
|
| /Documentation/networking/ |
| D | netif-msg.rst | 21 The message level was not precisely defined past level 3, but were
|
| /Documentation/filesystems/ |
| D | fiemap.rst | 95 length to extend past the request. Unless FIEMAP_EXTENT_NOT_ALIGNED is
120 This is generally the last extent in the file. A mapping attempt past
|
| D | cramfs.rst | 25 filesystem is allowed to extend past 256MB.)
|
| /Documentation/process/ |
| D | kernel-driver-statement.rst | 24 today, have in the past, or will in the future.
|
| D | botching-up-ioctls.rst | 9 One clear insight kernel graphics hackers gained in the past few years is that
63 past) then you need a driver feature flag or revision number somewhere.
|
| D | kernel-enforcement-statement.rst | 53 we might work for today, have in the past, or will in the future.
|
| D | embargoed-hardware-issues.rst | 91 issues in the past and has the necessary mechanisms in place to allow
186 security issues in the past.
|
| /Documentation/ABI/testing/ |
| D | sysfs-block-bcache | 47 For backing devices: Threshold past which sequential IO will
|
| /Documentation/locking/ |
| D | lockdep-design.rst | 176 took any hardirq-unsafe lock in the past.
179 any softirq-unsafe lock in the past.
182 hardirq-safe lock took it in the past.
185 softirq-safe lock took it in the past.
|
| /Documentation/dev-tools/kunit/ |
| D | faq.rst | 84 filesystem mounted), and has had issues in the past when built statically and
|
| /Documentation/core-api/ |
| D | timekeeping.rst | 123 may be as much as 10ms in the past (for CONFIG_HZ=100), same as
|
| /Documentation/security/ |
| D | self-protection.rst | 154 The classic stack buffer overflow involves writing past the expected end
192 traditionally leads to being able to write past the end of kernel buffers.
|
| /Documentation/devicetree/ |
| D | overlay-notes.rst | 128 or its content but these pointers must not persist past the notifier callback
|
| /Documentation/PCI/ |
| D | boot-interrupts.rst | 18 did not support the IO-APIC and for boot. Intel in the past has used the
|
| /Documentation/admin-guide/laptops/ |
| D | sonypi.rst | 79 events. If the driver worked for you in the past
|
| /Documentation/power/ |
| D | suspend-and-interrupts.rst | 20 block interrupts from them anyway. Also, in the past we had problems with
|
1234