Home
last modified time | relevance | path

Searched full:had (Results 1 – 25 of 3026) sorted by relevance

12345678910>>...122

/kernel/linux/linux-5.10/Documentation/driver-api/usb/
Dpersist.rst29 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
/kernel/linux/linux-4.19/Documentation/driver-api/usb/
Dpersist.rst29 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
/kernel/linux/linux-5.10/Documentation/arm/nwfpe/
Dnotes.rst16 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,
/kernel/linux/linux-4.19/Documentation/arm/nwfpe/
DNOTES13 f4 had been converted to an extended value in the emulator.
15 This is a side effect of the stfe instruction. The double in f4 had to be
16 converted to extended, then stored. If an lfm/sfm combination had been used,
/kernel/linux/linux-4.19/Documentation/filesystems/
Ddirectory-locking72 the order until we had acquired all locks).
101 would have a contended child and we had assumed that no object is its
109 to (2) the order hadn't changed since we had acquired filesystem lock.
122 new parent had been equal to or a descendent of source since the moment when
123 we had acquired filesystem lock and rename() would fail with -ELOOP in that
Dporting125 FS_SINGLE is gone (actually, that had happened back when ->get_sb()
208 ->revalidate() is gone. If your filesystem had it - provide ->getattr()
209 and let it call whatever you had as ->revlidate() + (for symlinks that
210 had ->revalidate()) add calls in ->follow_link()/->readlink().
218 * we know that parent had been locked (e.g. we are looking at
224 had been relying on BKL and that's prone to screwups. Old tree had quite
316 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
354 via rcu-walk path walk (basically, if the file can have had a path name in the
535 it's a symlink. Checking ->i_mode is really needed now. In-tree we had
/kernel/linux/linux-5.10/Documentation/filesystems/
Ddirectory-locking.rst82 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
/kernel/linux/linux-5.10/include/net/
Dinet_frag.h158 #define IPFRAG_ECN_NOT_ECT 0x01 /* one frag had ECN_NOT_ECT */
159 #define IPFRAG_ECN_ECT_1 0x02 /* one frag had ECN_ECT_1 */
160 #define IPFRAG_ECN_ECT_0 0x04 /* one frag had ECN_ECT_0 */
161 #define IPFRAG_ECN_CE 0x08 /* one frag had ECN_CE */
/kernel/linux/linux-4.19/include/net/
Dinet_frag.h149 #define IPFRAG_ECN_NOT_ECT 0x01 /* one frag had ECN_NOT_ECT */
150 #define IPFRAG_ECN_ECT_1 0x02 /* one frag had ECN_ECT_1 */
151 #define IPFRAG_ECN_ECT_0 0x04 /* one frag had ECN_ECT_0 */
152 #define IPFRAG_ECN_CE 0x08 /* one frag had ECN_CE */
/kernel/linux/linux-4.19/arch/mips/include/asm/octeon/
Dcvmx-wqe.h333 * than allowed and had an FCS error.
338 * and had an FCS error (100M and 10M only).
340 * than allowed and had an FCS error.
341 * - 7 = GMX FCS error: the RGMII packet had an FCS
345 * - 9 = extend error: the RGMII packet had an extend
347 * - 10 = length mismatch error: the RGMII packet had
351 * packet had one or more data reception errors
352 * (RXERR) or the SPI4 packet had one or more
359 * RGMII packet had a studder error (data not
362 * - 16 = FCS error: a SPI4.2 packet had an FCS error.
/kernel/linux/linux-5.10/arch/mips/include/asm/octeon/
Dcvmx-wqe.h333 * than allowed and had an FCS error.
338 * and had an FCS error (100M and 10M only).
340 * than allowed and had an FCS error.
341 * - 7 = GMX FCS error: the RGMII packet had an FCS
345 * - 9 = extend error: the RGMII packet had an extend
347 * - 10 = length mismatch error: the RGMII packet had
351 * packet had one or more data reception errors
352 * (RXERR) or the SPI4 packet had one or more
359 * RGMII packet had a studder error (data not
362 * - 16 = FCS error: a SPI4.2 packet had an FCS error.
/kernel/linux/linux-5.10/Documentation/ABI/removed/
Dvideo13947 alternative to raw1394's isochronous I/O functionality which had
8 performance issues in its first generation. Any video1394 user had
/kernel/linux/linux-4.19/Documentation/ABI/removed/
Dvideo13947 alternative to raw1394's isochronous I/O functionality which had
8 performance issues in its first generation. Any video1394 user had
/kernel/linux/linux-4.19/Documentation/block/
Dbiovecs.txt53 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.
/kernel/linux/linux-5.10/Documentation/block/
Dbiovecs.rst53 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.
/kernel/linux/linux-4.19/fs/btrfs/tests/
Dextent-buffer-tests.c19 char *value = "mary had a little lamb"; in test_btrfs_split_item()
20 char *split1 = "mary had a little"; in test_btrfs_split_item()
23 char *split4 = " had a little"; in test_btrfs_split_item()
84 * 'mary had a little' in test_btrfs_split_item()
/kernel/linux/linux-5.10/fs/btrfs/tests/
Dextent-buffer-tests.c19 char *value = "mary had a little lamb"; in test_btrfs_split_item()
20 char *split1 = "mary had a little"; in test_btrfs_split_item()
23 char *split4 = " had a little"; in test_btrfs_split_item()
83 * 'mary had a little' in test_btrfs_split_item()
/kernel/linux/linux-5.10/drivers/block/paride/
DTransition-notes74 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
/kernel/linux/linux-4.19/drivers/block/paride/
DTransition-notes74 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
/kernel/linux/linux-4.19/drivers/base/firmware_loader/
Dfallback.h16 * as if one had enabled CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y.
20 * This emulates the behaviour as if we had set the kernel
/kernel/linux/linux-5.10/drivers/base/firmware_loader/
Dfallback.h16 * as if one had enabled CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y.
20 * This emulates the behaviour as if we had set the kernel
/kernel/linux/linux-5.10/Documentation/process/
Dstable-api-nonsense.rst60 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
/kernel/linux/linux-4.19/Documentation/process/
Dstable-api-nonsense.rst60 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
/kernel/linux/linux-4.19/arch/arm/mach-rpc/
Dtime.c48 * We have not had an interrupt between reading count1 in ioc_timer_gettimeoffset()
55 * We have just had another interrupt between reading in ioc_timer_gettimeoffset()
/kernel/linux/linux-5.10/drivers/media/test-drivers/vidtv/
Dvidtv_common.c45 …pr_err_ratelimited("overflow detected, skipping. Try increasing the buffer size. Needed %zu, had %… in vidtv_memcpy()
81 …pr_err_ratelimited("overflow detected, skipping. Try increasing the buffer size. Needed %zu, had %… in vidtv_memset()

12345678910>>...122