On Wed, Apr 30, 2025 at 9:59 PM Lorenzo Stoakes <lorenzo.stoakes@xxxxxxxxxx> wrote: > A driver can specify either .mmap_proto(), .mmap() or both. This provides > maximum flexibility. Just to check I understand the intent correctly: The idea here is that .mmap_proto() is, at least for now, only for drivers who want to trigger merging, right? If a driver doesn't need merging, the normal .mmap() handler can still do all the things it was able to do before (like changing the ->vm_file pointer through vma_set_file(), or changing VMA flags in allowed ways)?
