covers: README row for the landed misc-next port

topics/stripe-alloc is 73 patches on misc-next now, not 39, and the port landed
2026-09-18.  The row also records what the cover itself still lacks -- prose for
patches 40-73 -- so the table does not read as "ready to send" when the cover
says otherwise, and notes the same-day rebase onto kdave misc-next 1397021ba66f3
after the old base was force-updated away.

Assisted-by: Claude:claude-opus-5[1m]

diff --git a/covers/README.md b/covers/README.md
index 77992c28ca69ddd50ee3343ef841ee9f9f585d3a..bdc181eeac22b08e94705fe4dbfaf1d18614350e 100644 (file)
--- a/covers/README.md
+++ b/covers/README.md
@@ -8,7 +8,7 @@ and may drift.  Reverified against the lane state on 2026-09-16 (both lanes reba
 
 | file | series | topic branch | state |
 |------|--------|--------------|-------|
-| `stripe-alloc.txt` | [RFC PATCH 0/39] raid56 stripe-exclusive allocation | `misc-next/topics/stripe-alloc` (39) | RFC; the 26-patch ENOSPC/relocation/reclaim chain and 6 review-round-1 fixes are LANDED on `6.18/topics/stripe-alloc` (72 commits, 2026-09-16); misc-next port + roadmap fold pending; open: the raid56-metadata log-epoch decision |
+| `stripe-alloc.txt` | [RFC PATCH 0/73] raid56 stripe-exclusive allocation | `misc-next/topics/stripe-alloc` (73) | RFC; the misc-next port LANDED 2026-09-18 (34 patches, one accounting term dropped and refixed, rebased onto kdave misc-next 1397021ba66f3 the same day); cover body still describes only patches 1-39 -- see the DO NOT SEND marker in it; open: the raid56-metadata log-epoch decision |
 | `raid56-rbio-fixes.txt` | [PATCH 0/2] two rbio-cache use-after-free races | last 2 of `misc-next/topics/raid56-fixes` (9) | ready to send |
 | `delalloc-fixes.txt` | [PATCH 0/2] delalloc range loses its space or data | `misc-next/topics/delalloc-fixes` (2) | ready to send; patch 1 Cc stable |
 | `compress-fixes.txt` | [PATCH 0/4] inode flags vs compression | `misc-next/topics/compress-fixes` (4; was 5, one superseded upstream) | ready to send |