diff --git a/README.md b/README.md
index e62299c..45520d6 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@ currently-supported upstream scoutfs version.
 Three patches against each supported scoutfs release:
 
 1. **Kmod core** — a per-mount 64 KiB ring of 64-byte notification records and
-   a single-reader drain ioctl (`SCOUTFS_IOC_READ_NOTIFY`, nr 25).  Emit is
+   a single-reader drain ioctl (`SCOUTFS_IOC_READ_NOTIFY`, nr 26).  Emit is
    non-blocking, drop-on-full; the monotonic `seq` field exposes drops to
    consumers.  Three percpu counters (`notify_emitted`,
    `notify_dropped_ring_full`, `notify_reader_attached`).  No mount option,
@@ -25,9 +25,11 @@ Three patches against each supported scoutfs release:
    clients.  Pure-stdlib Go; no external module dependencies.  Shipped
    with a systemd template unit `scoutfs-notifyd@<mountpoint>.service`.
 
-The notify ABI (`SCOUTFS_IOC_READ_NOTIFY` nr 25, 64-byte event record) is
-identical across all three supported scoutfs versions, so consumers and
-the daemon do not need per-version branching in their own code.
+The 64-byte event record layout is identical on every branch, so
+consumers and the daemon do not need per-version branching in their own
+code.  The ioctl number is not: it is nr 25 on `v1.28`-`v1.30` and nr 26
+on `v1.32`, because upstream v1.32 took nr 25 for
+`SCOUTFS_IOC_INJECT_TOTL_DELTA`.
 
 ## Repository layout
 
@@ -40,6 +42,7 @@ NOT apply cross-version without rebasing.
 | `v1.28`        | `v1.28`         | `v1.28-notify-1` |
 | `v1.29`        | `v1.29`         | `v1.29-notify-1` |
 | `main` / `v1.30` | `v1.30`       | `v1.30-notify-1` |
+| `v1.32`        | `v1.32`         | `v1.32-notify-1` |
 
 `main` tracks the newest supported scoutfs version.  When a new scoutfs
 release ships, a new branch is created and the patches are rebased onto