On Sun, Jul 12, 2026 at 11:44:54AM -0400, Gregory Price wrote: > The dax kmem driver onlines memory during probe using the system > default policy, with no atomic control for the state of an entire > region at runtime - only by toggling individual memory blocks. >
Took a look at Sashiko reviews. All are either false-positive, pre-existing issues on isolated patches that are actually resolved by later patches, or something we previously agreed on (WARN/pass in phase 2 of offline_and_remove_memory_ranges). So series is clean as-is. ~Gregory
