lkml.org 
[lkml]   [2024]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC PATCH v3 3/4] Introduce cpu_dcache_is_aliasing() across all architectures
    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@vger.kernel.org on the other patches. But the missing
    > context is just confusing. And I forgot to CC linux-fsdevel@vger.kernel.org
    > on patch 3 as well.
    >
    > You can find the entire series on lore:
    >
    > https://lore.kernel.org/lkml/20240131162533.247710-1-mathieu.desnoyers@efficios.com/T/#t
    >
    > I'll make sure to copy all lists for all patches in the next
    > round, namely:
    >
    > Cc: linux-arch@vger.kernel.org
    > Cc: linux-cxl@vger.kernel.org
    > Cc: linux-fsdevel@vger.kernel.org
    > Cc: linux-mm@kvack.org
    > Cc: linux-xfs@vger.kernel.org
    > Cc: dm-devel@lists.linux.dev
    > Cc: nvdimm@lists.linux.dev
    >
    > 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?

    \
     
     \ /
      Last update: 2024-05-27 14:43    [W:5.056 / U:0.576 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site