Searched full:did (Results  1 – 25 of 182) sorted by relevance
12345678
| /Documentation/scheduler/ | 
| D | sched-stats.rst | 86         the load did not require balancing when the cpu was idle 95     7)  # of times in this domain sched_balance_rq() was called but did 102         load did not require balancing when busy 110     15) # of times in this domain sched_balance_rq() was called but did not 118         load did not require balancing when the cpu was just becoming idle 126     23) # of times in this domain sched_balance_rq() was called but did not
  | 
| /Documentation/driver-api/ | 
| D | isa.rst | 62 behaviour of always loading as it inadvertently did for a bit after the 103 Then, if the driver did not provide a .match, it matches. If it did, 106 If it did **not** match, dev->platform_data is reset to indicate this to
  | 
| /Documentation/ABI/testing/ | 
| D | sysfs-bus-fsi-devices-sbefifo | 6 		timeout; i.e. the SBE did not respond within the time allotted
  | 
| D | debugfs-ec | 21   not get switched on again after you did a wrong write.
  | 
| D | sysfs-devices-xenbus | 28 		Number of events received for a Xen pv device which did not
  | 
| /Documentation/arch/sh/ | 
| D | booting.rst | 7   address of the device tree blob in r4. Since legacy bootloaders did not
  | 
| /Documentation/ABI/removed/ | 
| D | video1394 | 9 	to use raw1394 + libraw1394 too because video1394 did not provide
  | 
| D | sysfs-selinux-disable | 16 	easier for systems with primitive bootloaders that did not allow for
  | 
| /Documentation/litmus-tests/rcu/ | 
| D | RCU+sync+free.litmus | 7  * follows a grace period, if it did not see writes that precede that grace
  | 
| /Documentation/admin-guide/ | 
| D | hw_random.rst | 103 Special thanks to Matt Sottek.  I did the "guts", he 104 did the "brains" and all the testing.
  | 
| /Documentation/infiniband/ | 
| D | user_mad.rst | 120   The old ib_umad interface did not allow setting the P_Key index for 121   MADs that are sent and did not provide a way for obtaining the P_Key
  | 
| /Documentation/networking/ | 
| D | x25.rst | 17 layer of the Linux kernel and therefore it did not concern itself with
  | 
| /Documentation/core-api/irq/ | 
| D | irqflags-tracing.rst | 38   complaint, try to figure out the assembly code we did not cover yet,
  | 
| D | irq-affinity.rst | 61 i.e counters for the CPU0-3 did not change.
  | 
| /Documentation/filesystems/ext4/ | 
| D | checksums.rst | 10 structures did not have space to fit a full 32-bit checksum, so only the
  | 
| /Documentation/userspace-api/ | 
| D | no_new_privs.rst | 6 its parent did not have.  The most obvious examples are setuid/setgid
  | 
| /Documentation/devicetree/bindings/timer/ | 
| D | arm,sp804.yaml | 68     # The original binding did not specify any clock names, and there is no
  | 
| /Documentation/userspace-api/media/mediactl/ | 
| D | media-request-ioc-queue.rst | 66     The request did not contain any buffers. All requests are required
  | 
| /Documentation/maintainer/ | 
| D | feature-and-driver-maintainers.rst | 147  - did not author any of the code 149    for the development rather than the company which did the work
  | 
| /Documentation/driver-api/media/ | 
| D | v4l2-intro.rst | 23 to do right and many drivers never did do it correctly.
  | 
| /Documentation/userspace-api/media/v4l/ | 
| D | planar-apis.rst | 15 Initially, V4L2 API did not support multi-planar buffers and a set of
  | 
| /Documentation/arch/arm64/ | 
| D | tagged-pointers.rst | 39 userspace application did not enable the AArch64 Tagged Address ABI may
  | 
| /Documentation/scsi/ | 
| D | lpfc.rst | 38   to the system. If the driver did not hide these conditions, i/o would be
  | 
| /Documentation/gpu/ | 
| D | vgaarbiter.rst | 8 they did on ISA. For more details see "PCI Bus Binding to IEEE Std 1275-1994 184 enhancing the kernel code to adapt as a kernel module and also did the
  | 
| /Documentation/w1/masters/ | 
| D | ds2490.rst | 69   host did not explain the problem.  My guess is a bug in either qemu
  | 
        12345678