linux-kernel - Re: [PATCH v4 tip/core/locking 0/4] Memory-barrier documentation updates

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]

Message-Id: <20131205.134406.2030493811398343882.davem@davemloft.net>
Date:	Thu, 05 Dec 2013 13:44:06 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	paulmck@...ux.vnet.ibm.com
Cc:	rostedt@...dmis.org, mingo@...nel.org, henrik@...tad.us,
	linux-kernel@...r.kernel.org, laijs@...fujitsu.com,
	dipankar@...ibm.com, akpm@...ux-foundation.org,
	mathieu.desnoyers@...icios.com, josh@...htriplett.org,
	niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org,
	dhowells@...hat.com, edumazet@...gle.com, darren@...art.com,
	fweisbec@...il.com, sbw@....edu
Subject: Re: [PATCH v4 tip/core/locking 0/4] Memory-barrier documentation
 updates

From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Date: Thu, 5 Dec 2013 10:18:34 -0800

> The situation that leads me to use a large CC list is when I am doing
> something that affects all architectures.  I could imagine keeping a
> smallish CC list, then forwarding or bouncing the email to the remaining
> maintainers  Would that work reasonably, or is there some better approach?

Please use linux-arch, that's what that list is for, notifying arch
maintainers of changes that basically have an impact on every target.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/