lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 31 Jan 2024 12:42:44 -0800
From: Dan Williams <dan.j.williams@...el.com>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Christoph Hellwig
	<hch@...radead.org>
CC: Dan Williams <dan.j.williams@...el.com>, Arnd Bergmann <arnd@...db.de>,
	Dave Chinner <david@...morbit.com>, <linux-kernel@...r.kernel.org>, "Andrew
 Morton" <akpm@...ux-foundation.org>, Linus Torvalds
	<torvalds@...ux-foundation.org>, <linux-mm@...ck.org>,
	<linux-arch@...r.kernel.org>, Vishal Verma <vishal.l.verma@...el.com>, "Dave
 Jiang" <dave.jiang@...el.com>, Matthew Wilcox <willy@...radead.org>, "Russell
 King" <linux@...linux.org.uk>, <linux-cxl@...r.kernel.org>,
	<nvdimm@...ts.linux.dev>, <linux-xfs@...r.kernel.org>,
	<dm-devel@...ts.linux.dev>, Linux-Fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [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@...r.kernel.org on the other patches. But the missing
> context is just confusing. And I forgot to CC linux-fsdevel@...r.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@...r.kernel.org
>      Cc: linux-cxl@...r.kernel.org
>      Cc: linux-fsdevel@...r.kernel.org
>      Cc: linux-mm@...ck.org
>      Cc: linux-xfs@...r.kernel.org
>      Cc: dm-devel@...ts.linux.dev
>      Cc: nvdimm@...ts.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?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ