Re: [RFC PATCH v3 3/4] Introduce cpu_dcache_is_aliasing() across all architectures

[Dan Williams]

Mathieu Desnoyers wrote:
> On 2024-01-31 12:17, Christoph Hellwig wrote:
> > So this is the third iteration and you still keep only sending patch
> > 3 to the list.  How is anyone supposed to review it if you don't send
> > them all the pieces?
> 
> My bad. I was aiming for not spamming mailing lists on unrelated patches. I did
> not CC linux-xfs@xxxxxxxxxxxxxxx on the other patches. But the missing
> context is just confusing. And I forgot to CC linux-fsdevel@xxxxxxxxxxxxxxx
> on patch 3 as well.
> 
> You can find the entire series on lore:
> 
> https://lore.kernel.org/lkml/20240131162533.247710-1-mathieu.desnoyers@xxxxxxxxxxxx/T/#t
> 
> I'll make sure to copy all lists for all patches in the next
> round, namely:
> 
>      Cc: linux-arch@xxxxxxxxxxxxxxx
>      Cc: linux-cxl@xxxxxxxxxxxxxxx
>      Cc: linux-fsdevel@xxxxxxxxxxxxxxx
>      Cc: linux-mm@xxxxxxxxx
>      Cc: linux-xfs@xxxxxxxxxxxxxxx
>      Cc: dm-devel@xxxxxxxxxxxxxxx
>      Cc: nvdimm@xxxxxxxxxxxxxxx
> 
> Thanks,
> 
> Mathieu

FWIW there are some developers and lists that want all patches and there
are some developers only want to see the one patch they are directly
copied on. I have a locally maintained list as I have discovered these
different preferences, but maybe MAINTAINERS could carry a flag to
indicate this to save the next person some time?