| /Documentation/core-api/ | 
| D | errseq.rst | 6 number of "subscribers" to tell whether it has changed since a previous 19 frequently, since we have so few bits to use as a counter. 22 a flag to tell whether the value has been sampled since a new value was 24 sampled it since the last time an error was recorded. 36 any new errors have occurred since that sampling was done, and atomically 39 can tell whether the value has changed since they last checked it. 44 has ever been an error set since it was first initialized. 57 far and whether he made any mistakes since they last asked. 111 whether one was made since they last checked, and the latest value 122         errseq_t since = errseq_sample(&wd.wd_err); [all …] 
 | 
| /Documentation/devicetree/bindings/iio/temperature/ | 
| D | melexis,mlx90632.yaml | 19   object temperature range for industrial applications. Since it can 27   Since measured object emissivity effects Infra Red energy emitted, 36   degree Celsius for human body measurement applications. Since it can 40   Since measured object emissivity effects Infra Red energy emitted,
  | 
| /Documentation/userspace-api/ | 
| D | ELF.rst | 20 interpreter. Other PT_INTERP headers are ignored (since Linux 2.4.11). 26 (since Linux 2.6.6). Other PT_GNU_STACK headers are ignored. 31 ELF interpreter's last PT_GNU_PROPERTY program header is used (since
  | 
| /Documentation/admin-guide/LSM/ | 
| D | SafeSetID.rst | 18 capabilities, since using file capabilities to run a program with elevated 19 privileges opens up possible security holes since any user with access to the 25 since CAP_SETUID allows changing to any user on the system, including the root 27 especially since programs often only call setuid() to drop privileges to a 38 of CAP_SETUID since the non-root program cannot take advantage of CAP_SETUID to 92 "Since setuid only affects the current process, and since the SELinux controls
  | 
| /Documentation/admin-guide/mm/ | 
| D | pagemap.rst | 21     * Bit  56    page exclusively mapped (since 4.2) 22     * Bit  57    pte is uffd-wp write-protected (since 5.13) (see 24     * Bit  58    pte is a guard region (since 6.15) (see madvise (2) man page) 26     * Bit  61    page is file-page or shared-anon (since 3.5) 30    Since Linux 4.0 only users with the CAP_SYS_ADMIN capability can get PFNs. 128     The page has not been accessed since it was marked idle (see 162    The page has been referenced since last LRU list enqueue/requeue. 207 always 12 at most architectures). Since Linux 3.11 their meaning changes 208 after first clear of soft-dirty bits. Since Linux 4.2 they are used for 298     have been written to since they were last marked and/or optionally write protect
  | 
| D | soft-dirty.rst | 19      written to since step 1. 29 This is so, since the pages are still mapped to physical memory, and thus all
  | 
| /Documentation/sound/cards/ | 
| D | hdspm.rst | 10 Full functionality has been added to the driver. Since some of 25 		since unused DMA channels are disabled and less memory is 74 		 where DMA reads/writes. Since of the bulk mode of PCI it is only 98 Since DSP-MADI-Mixer has 8152 Fader, it does not make sense to 99 use the standard mixer-controls, since this would break most of 105 hwdep-interface. Since it could be a performance problem always 133 		  frequency or slave), since even not using an Audio-application 168 		 Note: Since MADI has a much higher bit-rate than word-clock, the 169 		 card should synchronise better in MADI Mode. But since the
  | 
| /Documentation/RCU/ | 
| D | UP.rst | 8 is that since there is only one CPU, it should not be necessary to 9 wait for anything else to get done, since there are no other CPUs for 45 RCU usage, since call_rcu() must wait for a grace period to elapse. 91 grace period has elapsed since those callbacks were queued.  This is 134 	then, since RCU callbacks can be invoked from softirq context, 139 	This restriction might seem gratuitous, since very few RCU
  | 
| /Documentation/admin-guide/ | 
| D | unicode.rst | 31 In particular, ESC ( U is no longer "straight to font", since the font 42 refers to this as a "Corporate Zone", since this is inaccurate for 44 point since it lets the direct-mapping area start on a large power of 72 omitted the scan 5 line, since it is also used as a block-graphics 81 since they are horribly vendor-specific.  This, of course, is an 106 Since the characters in the beginning of the Linux CZ have been more 122 However, since the set of symbols appear to be consistent throughout, 175 Since the assignment of the Klingon Linux Unicode block, a registry of
  | 
| D | iostats.rst | 5 Since 2.4.20 (and some versions before, with patches), and 2.5.45, 53 All fields except field 9 are cumulative since boot.  Field 9 should 101     Since 5.0 this field counts jiffies when at least one request was 108     (field 9) times the number of milliseconds spent doing I/O since the 146 Since 4.19 request times are measured with nanoseconds precision and 175 Note that since the address is translated to a disk-relative one, and no 183 reads/writes before merges for partitions and after for disks. Since a 189 disk and partition statistics are consistent again. Since we still don't
  | 
| D | syscall-user-dispatch.rst | 14 falls short on this task, since it has limited support to efficiently 37 since they are quite rare, at least for modern gaming applications. 39 Since this mechanism is designed to capture syscalls issued by 87 should not be seen as a security mechanism, since it is trivial for a
  | 
| /Documentation/ABI/obsolete/ | 
| D | sysfs-bus-iio | 7 		Since Kernel 5.11, multiple buffers are supported. 19 		Since Kernel 5.11, multiple buffers are supported. 31 		Since kernel 5.11 the scan_elements attributes are merged into 66 		Since kernel 5.11 the scan_elements attributes are merged into 108 		Since kernel 5.11 the scan_elements attributes are merged into 147 		Since kernel 5.11 the scan_elements attributes are merged into 168 		Since Kernel 5.11, multiple buffers are supported. 183 		Since Kernel 5.11, multiple buffers are supported.
  | 
| /Documentation/power/ | 
| D | suspend-and-cpuhotplug.rst | 157 argument. But during suspend, since the tasks are already frozen by the time 197    In this case since we probably need to apply different microcode revisions 212    Hence, when a new CPU is brought online, since the kernel finds that it 232    when the CPUs are brought back online, since they wouldn't have lost the 236    However, in the case of hibernation, since all the CPUs are completely 247    And during the CPU online operations (during resume/restore), since the 266    This might not reflect the true current state of the system, since the 277       into the kernel, since the freezing has not yet begun.
  | 
| /Documentation/process/ | 
| D | botching-up-ioctls.rst | 13 Which is nice, since there's no more insanity in the form of fake-generic, but 46    conversion or worse, fiddle the raw __u64 through your code since that 57 pain. And since getting things wrong on the first attempt is guaranteed you 62    rejecting the new flags/modes or ioctls (since doing that was botched in the 68    but isn't a complete solution since newer userspace on older kernels won't 74    future extensions is going right down the gutters since someone will submit 155    frame counter. With a spec lawyer hat on this isn't a bug since timeouts can 220 Finally, the name of the game is to get it right on the first attempt, since if
  | 
| /Documentation/filesystems/ | 
| D | directory-locking.rst | 167 Since the locking order is consistent with the ranking, all 195 have changed since the moment directory locks had been acquired, 199 Since all operations are on the same filesystem, there can't be 218 It can't be the parents - indeed, since D1 is an ancestor of Dn, 225 a loop, since the parents are locked before the children, so the parent 233 among the children, in some order.  But that is also impossible, since 236 That concludes the proof, since the set of operations with the 255 Suppose after the operation there is a loop; since there hadn't been such 260 Since the operation has succeeded, neither source nor target could have
  | 
| /Documentation/arch/powerpc/ | 
| D | elf_hwcaps.rst | 81     Unused in the kernel since f0ed73f3fa2c ("powerpc: Remove PowerPC 601") 94     Unused in the kernel since 732b32daef80 ("powerpc: Remove core support for 40x") 99     Unused in the kernel since 39c8bf2b3cc1 ("powerpc: Retire e200 core (mpc555x processor)") 115     Unused in the kernel since f0ed73f3fa2c ("powerpc: Remove PowerPC 601") 119     POWER4 support dropped from the kernel since 471d7ff8b51b ("powerpc/64s: Remove POWER4 support")
  | 
| /Documentation/locking/ | 
| D | rt-mutex-design.rst | 38 meantime, B executes, and since B is of a higher priority than C, it preempts C, 69 of A.  So now if B becomes runnable, it would not preempt C, since C now has 102            process.  Since the scope of the waiter is within the code for 133 would never diverge, since a process can't be blocked on more than one 161 Since a process may own more than one mutex, but never be blocked on more than 176 Also since a mutex may have more than one process blocked on it, we can 228 defined.  But is very complex to figure it out, since it depends on all 293 Now since mutexes can be defined by user-land applications, we don't want a DOS 305 mutex is not owned, this owner is set to NULL.  Since all architectures 332 This is really nice to have, since it allows you to only update a variable [all …] 
 | 
| /Documentation/devicetree/bindings/iommu/ | 
| D | apple,sart.yaml | 16   special support in the consumer driver is required since not all DMA 19   SART1 has first been used since at least the A11 (iPhone 8 and iPhone X)
  | 
| /Documentation/scsi/ | 
| D | ChangeLog.sym53c8xx | 70 	  This parameter wasn't that clever since we can use "sync:"  216 	  Code moved from the FreeBSD sym_hipd driver, since it has  219 	  function chips, since I cannot make sure for what chip revisions  230 	  io_request_lock since it seems to be a definite feature now.:) 231 	- Change get_pages by GetPages since Linux >= 2.3.27 now wants  254 	- Remove the quirk handling that has been useless since day one. 344 	  result is greater than 37 MHz. Since the precision of the  388 	- Do a normal soft reset as first chip reset, since aborting current  389 	  operation may raise an interrupt we are not able to handle since  404 	  the scatterlist instead of the data.:) Since this should never [all …] 
 | 
| /Documentation/fb/ | 
| D | tgafb.rst | 17 Major new features since Linux 2.0.x: 23 User-visible changes since Linux 2.2.x: 58 The XFree86 FBDev server has been reported not to work, since tgafb doesn't do
  | 
| /Documentation/ABI/removed/ | 
| D | sysfs-mce | 6 		checks (see last sentence below) and those are present since 18 		Since machine check exceptions can happen any time it is
  | 
| /Documentation/devicetree/bindings/serio/ | 
| D | ps2-gpio.yaml | 20       from <dt-bindings/gpio/gpio.h> since the signal is open drain by 28       from <dt-bindings/gpio/gpio.h> since the signal is open drain by
  | 
| /Documentation/ABI/testing/ | 
| D | configfs-stp-policy-p_sys-t | 29 		passed since the previous packet from this source. Zero is 37 		this many milliseconds have passed since the previous
  | 
| /Documentation/translations/zh_CN/core-api/ | 
| D | errseq.rst | 112         errseq_t since = errseq_sample(&wd.wd_err); 114         err = errseq_check(&wd.wd_err, since); 116 由于他只是要在那个点之后丢弃 ``since`` ,所以他不需要在这里推进它。同时他也不需要
  | 
| /Documentation/admin-guide/cgroup-v1/ | 
| D | hugetlb.rst | 76 control group and enforces the limit during page fault. Since HugeTLB 96 HugeTLB memory for which no reservation exists. Since reservation limits are 103 Reservation limits are superior to page fault limits described above, since 108 hard to avoid processes getting SIGBUS since the sysadmin needs precisely know
  |