| /linux/Documentation/arch/arm/nwfpe/ |
| H A 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/Documentation/ABI/removed/ |
| H A 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/Documentation/driver-api/usb/ |
| H A 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/Documentation/locking/ |
| H A 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.
|
| H A 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.
|
| /linux/Documentation/filesystems/ |
| H A 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
|
| /linux/scripts/ |
| H A D | checksyscalls.sh | 243 /* sync_file_range had a stupid ABI. Allow sync_file_range2 instead */
|
| /linux/Documentation/scsi/ |
| H A 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
|
| /linux/Documentation/sound/soc/ |
| H A D | overview.rst | 9 had some limitations:-
13 Linux had different wm8731 drivers for 4 different SoC platforms.
|
| /linux/net/mpls/ |
| H A D | Kconfig | 23 that have had MPLS stack entries pushed onto them and thus
|
| /linux/arch/x86/lib/ |
| H A D | checksum_32.S | 71 jae 1f # Jump if we had at least two bytes.
285 jae 1f # Jump if we had at least two bytes.
|
| /linux/arch/sh/lib/ |
| H A D | checksum.S | 56 bt/s 1f ! Jump if we had at least two bytes.
179 cmp/pz r6 ! Jump if we had at least two bytes.
|
| /linux/Documentation/process/ |
| H A 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/Documentation/admin-guide/device-mapper/ |
| H A D | cache-policies.rst | 80 levels generally had the most entries, and the top ones had very
|
| /linux/Documentation/arch/arm/sa1100/ |
| H A D | serial_uart.rst | 5 The SA1100 serial port had its major/minor numbers officially assigned::
|
| /linux/Documentation/timers/ |
| H A 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/drivers/usb/core/ |
| H A D | Kconfig | 26 devices that lose power get reenumerated as if they had been
116 The default value Linux has always had is 2 seconds. Change
|
| /linux/Documentation/sound/designs/ |
| H A 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/Documentation/virt/kvm/s390/ |
| H A 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
|
| /linux/fs/ceph/ |
| H A D | caps.c | 584 unsigned had = __ceph_caps_issued(ci, NULL); in __check_cap_issue() local
594 (had & (CEPH_CAP_FILE_CACHE|CEPH_CAP_FILE_LAZYIO)) == 0) { in __check_cap_issue()
604 if ((issued & CEPH_CAP_FILE_SHARED) != (had & CEPH_CAP_FILE_SHARED)) { in __check_cap_issue()
614 if (S_ISDIR(ci->netfs.inode.i_mode) && (had & CEPH_CAP_DIR_CREATE) && in __check_cap_issue()
3233 static void __ceph_put_cap_refs(struct ceph_inode_info *ci, int had, in __ceph_put_cap_refs() argument
3242 if (had & CEPH_CAP_PIN) in __ceph_put_cap_refs()
3244 if (had & CEPH_CAP_FILE_RD) in __ceph_put_cap_refs()
3247 if (had & CEPH_CAP_FILE_CACHE) in __ceph_put_cap_refs()
3250 if (had & CEPH_CAP_FILE_EXCL) in __ceph_put_cap_refs()
3253 if (had & CEPH_CAP_FILE_BUFFER) { in __ceph_put_cap_refs()
[all …]
|
| /linux/drivers/mtd/nand/ |
| H A D | Kconfig | 36 The original Linux implementation had byte 0 and 1 swapped.
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | bigalloc.rst | 30 block, even for directories. TaoBao had a patchset to extend the “use
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm_tis.rst | 12 drivers. Originally Linux had only a driver called tpm_tis, which covered
|
| /linux/Documentation/mm/ |
| H A D | free_page_reporting.rst | 35 registered it is possible for it to resume where the previous driver had
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-pxa-pci-ce4100.txt | 22 non-zero if you had 2 or more devices mapped off
|