From ce085b8e3ba744270fde3ee03115863dce0b06b6 Mon Sep 17 00:00:00 2001 From: enricobuehler Date: Thu, 16 Jul 2026 15:24:36 +0200 Subject: [PATCH] style(vdisplay): dedupe the attach-block comment (first-frame stash follow-up) Comment-only: the lazy-attach comment carried the delivery-consumption sentence twice after the stash rework. Co-Authored-By: Claude Fable 5 --- .../drivers/pf-vdisplay/src/swap_chain_processor.rs | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/packaging/windows/drivers/pf-vdisplay/src/swap_chain_processor.rs b/packaging/windows/drivers/pf-vdisplay/src/swap_chain_processor.rs index 7283830a..c2e33ba0 100644 --- a/packaging/windows/drivers/pf-vdisplay/src/swap_chain_processor.rs +++ b/packaging/windows/drivers/pf-vdisplay/src/swap_chain_processor.rs @@ -318,12 +318,10 @@ impl SwapChainProcessor { // cheap mutex peek, the same cost the pending-delivery check above already pays): attach // latency is now first-frame latency, since the attach itself republishes the stash. A // taken delivery is consumed whether the attach succeeds or not (on failure its handles are - // closed, the host's wait-for-attach reads the status code, and any retry is a NEW delivery). - // A failed attach only drops the delivery (its handles are closed inside from_channel; - // the host's wait-for-attach reads the status code, and any retry is a NEW delivery). - // `target_id` binds the attach: the mapped ring must name THIS monitor (proto v3 - // validation inside from_channel — a cross-delivered ring is refused, never published - // into). + // closed inside from_channel, the host's wait-for-attach reads the status code, and any + // retry is a NEW delivery). `target_id` binds the attach: the mapped ring must name THIS + // monitor (proto v3 validation inside from_channel — a cross-delivered ring is refused, + // never published into). if publisher.is_none() && let Some(channel) = crate::monitor::take_frame_channel(target_id) && let Ok(mut p) = FramePublisher::from_channel(