Searched full:had (Results 1 – 25 of 232) sorted by relevance
12345678910
| /Documentation/arch/arm/nwfpe/ |
| D | notes.rst | 16 f4 had been converted to an extended value in the emulator.
18 This is a side effect of the stfe instruction. The double in f4 had to be
19 converted to extended, then stored. If an lfm/sfm combination had been used,
|
| /Documentation/ABI/removed/ |
| D | video1394 | 7 alternative to raw1394's isochronous I/O functionality which had
8 performance issues in its first generation. Any video1394 user had
|
| /Documentation/driver-api/usb/ |
| D | persist.rst | 29 though they had disconnected. This is always safe and it is the
39 devices. The effect is exactly the same as if the device really had
40 been unplugged while the system was suspended. If you had a mounted
52 it's as though you had unplugged all the USB devices. Yes, it's
78 reset or otherwise had lost power) then it applies a persistence check
87 kernel treats the device as though it had merely been reset instead of
97 behaves as though the old device had been unplugged and a new device
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 192 if all operations had been of the "lock parent, then child" sort
195 have changed since the moment directory locks had been acquired,
211 all of them had been stable.
224 It can't be a parent and its child; otherwise we would've had
247 in between (all of those would fail with -ENOTEMPTY, had they ever gotten
257 had its parent changed. In other words, the loop must be passing through
264 not have passed through the node itself, or we would've had a loop before
|
| D | porting.rst | 148 FS_SINGLE is gone (actually, that had happened back when ->get_sb()
237 ->revalidate() is gone. If your filesystem had it - provide ->getattr()
238 and let it call whatever you had as ->revlidate() + (for symlinks that
239 had ->revalidate()) add calls in ->follow_link()/->readlink().
249 * we know that parent had been locked (e.g. we are looking at
256 had been relying on BKL and that's prone to screwups. Old tree had quite
355 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
399 via rcu-walk path walk (basically, if the file can have had a path name in the
667 it's a symlink. Checking ->i_mode is really needed now. In-tree we had
1002 the superblock had been removed from the list of superblocks of the
[all …]
|
| /Documentation/block/ |
| D | biovecs.rst | 55 it had to walk two different bios at the same time, keeping both bi_idx and
63 * Before, any code that might need to use the biovec after the bio had been
65 it somewhere else if there was an error) had to save the entire bvec array
85 bcache) had some ugly workarounds for this.
|
| /Documentation/sound/soc/ |
| D | overview.rst | 9 had some limitations:-
13 Linux had different wm8731 drivers for 4 different SoC platforms.
|
| /Documentation/process/ |
| D | stable-api-nonsense.rst | 60 Assuming that we had a stable kernel source interface for the kernel, a
132 which have had to maintain their older USB interfaces over time. This
139 relatively little pain. If Linux had to ensure that it will preserve a
141 the older, broken one would have had to be maintained over time, leading
|
| /Documentation/sphinx/ |
| D | parallel-wrapper.sh | 16 # target has had.
|
| /Documentation/networking/ |
| D | tls.rst | 239 this will look like TLS records had been tampered with and will result
251 If the record decrypted turns out to had been padded or is not a data
282 number of RX records which had to be re-decrypted due to
287 number of data RX records which had to be re-decrypted due to
|
| /Documentation/timers/ |
| D | hrtimers.rst | 108 settimeofday and NTP, all the timers (!) had to be dequeued, the
109 time-changing code had to fix them up one by one, and all of them had to
|
| /Documentation/filesystems/ext4/ |
| D | bigalloc.rst | 30 block, even for directories. TaoBao had a patchset to extend the “use
|
| /Documentation/admin-guide/device-mapper/ |
| D | cache-policies.rst | 80 levels generally had the most entries, and the top ones had very
|
| /Documentation/scsi/ |
| D | scsi-generic.rst | 76 Here is a list of Linux kernels in the 2.4 series that had the new version
87 For reference here is a list of Linux kernels in the 2.2 series that had
|
| /Documentation/mm/ |
| D | free_page_reporting.rst | 35 registered it is possible for it to resume where the previous driver had
|
| /Documentation/locking/ |
| D | lockstat.rst | 53 - number of lock acquisitions that had to wait
56 - shortest (non-0) time we ever had to wait for a lock
58 - longest time we ever had to wait for a lock
81 that had to wait on lock acquisition.
|
| D | robust-futexes.rst | 63 approach had been pending for years, but they are still not completely
84 So something had to be done.
160 userspace had to do.
|
| /Documentation/arch/arm/sa1100/ |
| D | serial_uart.rst | 5 The SA1100 serial port had its major/minor numbers officially assigned::
|
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 20 The problem, so far, was that we had no standard channel map
21 explicitly, and applications had no way to know which channel
|
| /Documentation/virt/kvm/s390/ |
| D | s390-pv.rst | 85 This also implies that the register content that a guest had in r<n>
110 is ignored and execution continues as if the guest instruction had
|
| /Documentation/security/tpm/ |
| D | tpm_tis.rst | 12 drivers. Originally Linux had only a driver called tpm_tis, which covered
|
| /Documentation/devicetree/bindings/clock/ |
| D | qcom,sdm845-dispcc.yaml | 23 # The code had to use hardcoded mechanisms to find the input clocks.
|
| /Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 45 the old value you had configured after the cache is set up.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-phydev | 15 device has had any "fixup" workaround running on it, encoded as
|
| /Documentation/crypto/ |
| D | descore-readme.rst | 84 improvements i had suggested to him, this package's
173 man pages either didn't exist or dumped core. i had heard of kerberos,
176 it was too convoluted, the code had been written without taking
179 it was excessively slow, the author had attempted to clarify the code
190 do the same - it was a trivial change from which i had been scared away
|
12345678910