Searched refs:had (Results 1 – 25 of 227) sorted by relevance
12345678910
| /Linux-v5.4/Documentation/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,
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | directory-locking.rst | 82 the order until we had acquired all locks).
111 would have a contended child and we had assumed that no object is its
119 to (2) the order hadn't changed since we had acquired filesystem lock.
132 new parent had been equal to or a descendent of source since the moment when
133 we had acquired filesystem lock and rename() would fail with -ELOOP in that
|
| D | porting.rst | 142 FS_SINGLE is gone (actually, that had happened back when ->get_sb()
231 ->revalidate() is gone. If your filesystem had it - provide ->getattr()
232 and let it call whatever you had as ->revlidate() + (for symlinks that
233 had ->revalidate()) add calls in ->follow_link()/->readlink().
243 * we know that parent had been locked (e.g. we are looking at
250 had been relying on BKL and that's prone to screwups. Old tree had quite
349 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
393 via rcu-walk path walk (basically, if the file can have had a path name in the
661 it's a symlink. Checking ->i_mode is really needed now. In-tree we had
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-handle.txt | 32 as clean up all its resources that it had used. The argument _tep_ is
39 it had used are cleaned up.
|
| /Linux-v5.4/scripts/ |
| D | checksyscalls.sh | 242 /* sync_file_range had a stupid ABI. Allow sync_file_range2 instead */
|
| /Linux-v5.4/drivers/block/paride/ |
| D | Transition-notes | 74 from pd.c. That could happen only if pi_do_claimed() had been
86 0 when pd_next_buf() had acquired pd_lock. If it become 0 while
88 the thread that had reset it would be in the area simulateously.
107 check its value is in ps_set_intr() and if it had been non-zero at that
|
| /Linux-v5.4/Documentation/block/ |
| D | biovecs.rst | 53 it had to walk two different bios at the same time, keeping both bi_idx and
61 * Before, any code that might need to use the biovec after the bio had been
63 it somewhere else if there was an error) had to save the entire bvec array
83 bcache) had some ugly workarounds for this.
|
| /Linux-v5.4/net/ax25/ |
| D | TODO | 12 The ax25_rt_find_route synopsys is pervert but I somehow had to deal with
|
| /Linux-v5.4/Documentation/sound/soc/ |
| D | overview.rst | 9 had some limitations:-
13 Linux had different wm8731 drivers for 4 different SoC platforms.
|
| /Linux-v5.4/net/mpls/ |
| D | Kconfig | 23 that have had MPLS stack entries pushed onto them and thus
|
| /Linux-v5.4/drivers/usb/core/ |
| D | Kconfig | 26 devices that lose power get reenumerated as if they had been
102 The default value Linux has always had is 2 seconds. Change
|
| /Linux-v5.4/Documentation/scsi/ |
| D | scsi-generic.txt | 73 Here is a list of linux kernels in the 2.4 series that had new version
83 For reference here is a list of linux kernels in the 2.2 series that had
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | adm1021.rst | 135 2003) microarchitecture had real MAX1617, ADM1021, or compatible chips
137 era (with 400 MHz FSB) had chips with only one temperature sensor.
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | cache-policies.rst | 80 levels generally had the most entries, and the top ones had very
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-net-phydev | 15 device has had any "fixup" workaround running on it, encoded as
|
| /Linux-v5.4/Documentation/arm/sa1100/ |
| D | serial_uart.rst | 5 The SA1100 serial port had its major/minor numbers officially assigned::
|
| /Linux-v5.4/Documentation/filesystems/ext4/ |
| D | bigalloc.rst | 30 block, even for directories. TaoBao had a patchset to extend the “use
|
| /Linux-v5.4/arch/sh/lib/ |
| D | checksum.S | 75 bt/s 1f ! Jump if we had at least two bytes.
230 cmp/pz r6 ! Jump if we had at least two bytes.
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/devicetree/bindings/i2c/ |
| D | i2c-pxa-pci-ce4100.txt | 22 non-zero if you had 2 or more devices mapped off
|
12345678910
