| /linux-6.8/tools/perf/pmu-events/arch/x86/lunarlake/ |
| D | memory.json | 10 …atch to completion is greater than 1024 cycles. Reported latency may be longer than just the memo…
23 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
36 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
49 …atch to completion is greater than 2048 cycles. Reported latency may be longer than just the memo…
62 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
75 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
88 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
101 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
114 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
127 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/kernel/printk/ |
| D | nbcon.c | 111 * Only to be used when the console is not yet or no longer visible in the
200 * If the specified record no longer exists, the oldest available record in nbcon_seq_force()
221 * nbcon_seq_force() was used or the current context no longer owns the
331 * or this context is no longer the waiter.
337 * except when this context is no longer the waiter.
685 * When this function returns false then the calling context no longer owns
686 * the console and is no longer allowed to go forward. In this case it must
687 * back out immediately and carefully. The buffer content is also no longer
688 * trusted since it no longer belongs to the calling context.
728 * The calling context no longer owns the console so go back all the in nbcon_context_can_proceed()
[all …]
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/graniterapids/ |
| D | memory.json | 10 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
22 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
34 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
46 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
58 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
70 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
82 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
94 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | memory.json | 26 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
38 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
50 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
62 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
74 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
86 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
98 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
110 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/include/uapi/linux/netfilter/ |
| D | nfnetlink_conntrack.h | 247 CTA_STATS_SEARCHED, /* no longer used */
249 CTA_STATS_NEW, /* no longer used */
251 CTA_STATS_IGNORE, /* no longer used */
252 CTA_STATS_DELETE, /* no longer used */
253 CTA_STATS_DELETE_LIST, /* no longer used */
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/meteorlake/ |
| D | memory.json | 148 …atch to completion is greater than 1024 cycles. Reported latency may be longer than just the memo…
161 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
174 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
187 …atch to completion is greater than 2048 cycles. Reported latency may be longer than just the memo…
200 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
213 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
226 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
239 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
252 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
265 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/Documentation/pcmcia/ |
| D | driver-changes.rst | 41 dev_info_t and a few other typedefs are removed. No longer use them
115 The irq_mask and irq_list parameters should no longer be used in
121 client->PendingEvents is no longer available.
127 * core functions no longer available (as of 2.6.11)
140 It is no longer necessary to iterate on the driver's internal
145 it no longer marks these resources busy. This means that driver
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/alderlake/ |
| D | memory.json | 123 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
136 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
149 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
162 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
175 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
188 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
201 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
214 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | memory.json | 60 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
72 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
84 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
96 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
108 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
120 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
132 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
144 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| D | memory.json | 60 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
72 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
84 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
96 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
108 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
120 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
132 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
144 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/drivers/gpu/drm/i915/gt/ |
| D | intel_reset_types.h | 28 * #I915_WEDGED - If reset fails and we can no longer use the GPU,
34 * longer use the GPU - similar to #I915_WEDGED bit. The difference in
39 * use it to mark that the GPU is no longer available (and prevent
|
| D | intel_engine_heartbeat.c | 43 long longer; in next_heartbeat() local
50 longer = READ_ONCE(engine->props.preempt_timeout_ms) * 2; in next_heartbeat()
51 longer = intel_clamp_heartbeat_interval_ms(engine, longer); in next_heartbeat()
52 if (longer > delay) in next_heartbeat()
53 delay = longer; in next_heartbeat()
|
| /linux-6.8/include/uapi/linux/ |
| D | tty_flags.h | 12 * [x] in the bit comments indicates the flag is defunct and no longer used.
39 * WARNING: These flags are no longer used and have been superceded by the
50 #define ASYNCB_SHARE_IRQ 24 /* for multifunction cards, no longer used */
85 /* These flags are no longer used (and were always masked from userspace) */
|
| /linux-6.8/tools/power/cpupower/lib/ |
| D | cpufreq.h | 84 * Remember to call cpufreq_put_driver when no longer needed
95 * Remember to call cpufreq_put_policy when no longer needed
142 * Remember to call cpufreq_put_affected_cpus when no longer needed
154 * Remember to call cpufreq_put_related_cpus when no longer needed
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/rocketlake/ |
| D | memory.json | 82 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
94 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
106 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
118 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
130 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
142 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
154 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
166 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/icelake/ |
| D | memory.json | 82 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
94 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
106 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
118 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
130 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
142 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
154 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
166 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | memory.json | 26 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
38 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
50 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
62 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
74 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
86 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
98 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
110 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux-6.8/Documentation/hwmon/ |
| D | it87.rst | 34 Datasheet: Once publicly available at the ITE website, but no longer
42 Datasheet: Once publicly available at the ITE website, but no longer
50 Datasheet: Once publicly available at the ITE website, but no longer
58 Datasheet: Once publicly available at the ITE website, but no longer
170 Datasheet: No longer be available
222 longer supports this interface though, as it is slower and less reliable
|
| /linux-6.8/tools/testing/selftests/net/hsr/ |
| D | hsr_ping.sh | 152 echo "INFO: Longer ping test."
158 stop_if_error "Longer ping test failed."
164 stop_if_error "Longer ping test failed."
170 stop_if_error "Longer ping test failed."
|
| /linux-6.8/Documentation/gpu/ |
| D | tegra.rst | 79 display controller can no longer drive all of the outputs. While two of these
103 longer do and instead provide standard interfaces such as DSI and eDP/DP.
110 This interface is no longer available since Tegra124. It has been replaced by
171 longer needed, it can be closed using the ``DRM_IOCTL_TEGRA_CLOSE_CHANNEL``
|
| /linux-6.8/include/linux/soc/apple/ |
| D | sart.h | 47 * @paddr: Start address of the region no longer used for DMA
48 * @size: Size of the region no longer used for DMA.
|
| /linux-6.8/Documentation/livepatch/ |
| D | system-state.rst | 14 change the system behavior or state so that it is no longer safe to
139 not longer needed.
156 - Remove any not longer needed setting or data.
|
| /linux-6.8/net/core/ |
| D | request_sock.c | 45 * to NULL when a TFO socket no longer needs to access the request_sock.
60 * NULL since it's no longer needed. More importantly, "req->sk == NULL"
73 * decremented by this function when fastopen_rsk is no longer needed.
|
| /linux-6.8/drivers/gpu/drm/nouveau/nvkm/engine/disp/ |
| D | hdmi.c | 20 * We presume that no valid frame is longer than 17 in pack_hdmi_infoframe()
22 * if it's longer. in pack_hdmi_infoframe()
|
| /linux-6.8/Documentation/ABI/testing/ |
| D | sysfs-platform-chipidea-usb-otg | 8 and to be 0 when the application no longer wants to use
40 bus as host, and is 0 when the application no longer wants to
|