| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-devices-physical_location | 3 Contact: Won Chung <wonchung@google.com>
11 Contact: Won Chung <wonchung@google.com>
18 Contact: Won Chung <wonchung@google.com>
25 Contact: Won Chung <wonchung@google.com>
32 Contact: Won Chung <wonchung@google.com>
39 Contact: Won Chung <wonchung@google.com>
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/progs/ |
| D | test_ksyms_weak.c | 57 /* dead code won't be seen by the verifier */ in pass_handler()
61 /* dead code won't be seen by the verifier */ in pass_handler()
65 /* dead code won't be seen by the verifier */ in pass_handler()
|
| /kernel/linux/linux-5.10/arch/riscv/lib/ |
| D | delay.c | 37 * 31 is the biggest scale shift value that won't overflow 32 bits for
61 * won't happen.
101 * This doesn't bother checking for overflow, as it won't happen (it's in ndelay()
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | dma-attributes.rst | 37 that you won't dereference the pointer returned by dma_alloc_attr(). You
87 - You know that the accesses to this memory won't thrash the TLB.
101 Setting this hint doesn't guarantee that you won't get huge pages, but it
102 means that we won't try quite as hard to get them.
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| D | dma-attributes.rst | 37 that you won't dereference the pointer returned by dma_alloc_attr(). You
87 - You know that the accesses to this memory won't thrash the TLB.
101 Setting this hint doesn't guarantee that you won't get huge pages, but it
102 means that we won't try quite as hard to get them.
|
| /kernel/linux/linux-6.6/arch/riscv/lib/ |
| D | delay.c | 41 * 31 is the biggest scale shift value that won't overflow 32 bits for
65 * won't happen.
105 * This doesn't bother checking for overflow, as it won't happen (it's in ndelay()
|
| /kernel/linux/linux-6.6/drivers/s390/char/ |
| D | uvdevice.c | 154 * are sane. Every other check is made by the Ultravisor (UV) and won't result
172 * UV will return invalid command rc. This won't be fenced in the driver
245 * (UV). Therefore UV errors won't result in a negative return
255 * invalid command rc. This won't be fenced in the driver and does not
301 * Every other check is made by the Ultravisor (UV) and won't result in a
308 * command rc. This won't be fenced in the driver and does not result in a
355 * command rc. This won't be fenced in the driver and does not result in a
|
| /kernel/linux/linux-6.6/arch/x86/kernel/ |
| D | doublefault_32.c | 41 * won't see it (no ENCODE_FRAME_POINTER), so a nested stack dump in doublefault_shim()
42 * won't successfully unwind to the source of the double fault. in doublefault_shim()
53 /* We won't go through the entry asm, so we can leave __csh as 0. */ in doublefault_shim()
|
| /kernel/linux/linux-6.6/drivers/usb/gadget/ |
| D | epautoconf.c | 41 * That second descriptor won't always be the same as the first one.
50 * and hardware won't be able to autoconfigure.
130 * That second descriptor won't always be the same as the first one.
138 * Some combinations of driver and hardware won't be able to autoconfigure.
|
| /kernel/linux/linux-5.10/drivers/usb/gadget/ |
| D | epautoconf.c | 41 * That second descriptor won't always be the same as the first one.
50 * and hardware won't be able to autoconfigure.
130 * That second descriptor won't always be the same as the first one.
138 * Some combinations of driver and hardware won't be able to autoconfigure.
|
| /kernel/linux/linux-5.10/arch/x86/kernel/ |
| D | doublefault_32.c | 40 * won't see it (no ENCODE_FRAME_POINTER), so a nested stack dump in doublefault_shim()
41 * won't successfully unwind to the source of the double fault. in doublefault_shim()
52 /* We won't go through the entry asm, so we can leave __csh as 0. */ in doublefault_shim()
|
| /kernel/linux/linux-5.10/drivers/mtd/parsers/ |
| D | Kconfig | 32 for your particular device. It won't happen automatically. The
94 for your particular device. It won't happen automatically. The
128 for your particular device. It won't happen automatically. The
|
| /kernel/linux/linux-6.6/drivers/power/reset/ |
| D | linkstation-poweroff.c | 64 /* Clear interrupts to ensure INTn won't be holded in high state */ in linkstation_mvphy_reg_intn()
69 * off, we won't be able to wake up by sending another magic packet. in linkstation_mvphy_reg_intn()
100 * off, we won't be able to wake up by sending another magic packet. in readynas_mvphy_set_reg()
|
| /kernel/linux/linux-5.10/arch/arc/kernel/ |
| D | entry-arcv2.S | 88 ; so a higher prio interrupt taken here won't clobber prev prio icause
219 ; AUX_IRQ_ACTIVE won't have U bit set (since intr in K mode), hence SP
220 ; won't be switched to correct U mode value (from AUX_SP)
246 ; IRQ RTIE won't reliably restore DE bit and/or BTA, needs workaround
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-g-topology.rst | 76 the ioctl won't store the entities. It will just update
91 the ioctl won't store the interfaces. It will just update
106 won't store the pads. It will just update ``num_pads``
120 won't store the links. It will just update ``num_links``
|
| /kernel/linux/linux-6.6/arch/arc/kernel/ |
| D | entry-arcv2.S | 89 ; so a higher prio interrupt taken here won't clobber prev prio icause
205 ; AUX_IRQ_ACTIVE won't have U bit set (since intr in K mode), hence SP
206 ; won't be switched to correct U mode value (from AUX_SP)
232 ; IRQ RTIE won't reliably restore DE bit and/or BTA, needs workaround
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-g-topology.rst | 76 the ioctl won't store the entities. It will just update
91 the ioctl won't store the interfaces. It will just update
106 won't store the pads. It will just update ``num_pads``
120 won't store the links. It will just update ``num_links``
|
| /kernel/linux/linux-5.10/Documentation/sound/hd-audio/ |
| D | controls.rst | 43 won't hear any PCM stream.
52 jacks. That is, the headphone won't auto-mute the other line-outs,
91 doesn't provide a proper jack-detection, this won't work; in such a
|
| /kernel/linux/linux-6.6/Documentation/sound/hd-audio/ |
| D | controls.rst | 43 won't hear any PCM stream.
52 jacks. That is, the headphone won't auto-mute the other line-outs,
91 doesn't provide a proper jack-detection, this won't work; in such a
|
| /kernel/linux/linux-6.6/arch/arm/common/ |
| D | vlock.S | 80 @ Check who won:
84 eor r0, r1, r2 @ zero if I won, else nonzero
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | ihex.h | 46 /* Check that ihex_next_binrec() won't take us off the end of the image... */
62 /* Request firmware and validate it so that we can trust we won't
|
| /kernel/linux/linux-5.10/arch/arm/common/ |
| D | vlock.S | 78 @ Check who won:
82 eor r0, r1, r2 @ zero if I won, else nonzero
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | ihex.h | 46 /* Check that ihex_next_binrec() won't take us off the end of the image... */
62 /* Request firmware and validate it so that we can trust we won't
|
| /kernel/linux/linux-6.6/drivers/mtd/parsers/ |
| D | Kconfig | 42 for your particular device. It won't happen automatically. The
123 for your particular device. It won't happen automatically. The
172 for your particular device. It won't happen automatically. The
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | bcache.rst | 33 Since random IO is what SSDs excel at, there generally won't be much benefit
54 you format your backing devices and cache device at the same time, you won't
110 /dev/bcache<N> device won't be created until the cache shows up - particularly
275 fdisk run and re-register a changed partition table, which won't work
278 1) Is it present in /dev/bcache* ? (there are times where it won't be)
284 2) But if your backing device is gone, this won't work::
389 a cache miss won't be able to insert a key for the new data and the data
390 won't be written to the cache.
|