linux-kernel - [PATCH tip/core/rcu 0/5] Documentation updates for 4.3

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-next>] [day] [month] [year] [list]

Message-ID: <20150717233224.GA24318@linux.vnet.ibm.com>
Date:	Fri, 17 Jul 2015 16:32:24 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	mingo@...nel.org, jiangshanlai@...il.com, dipankar@...ibm.com,
	akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
	josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
	rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
	dvhart@...ux.intel.com, fweisbec@...il.com, oleg@...hat.com,
	bobby.prani@...il.com
Subject: [PATCH tip/core/rcu 0/5] Documentation updates for 4.3

Hello!

This series contains documentation updates for 4.3:

1.	Bring rcutorture parameters up to date.

2.	Fix spelling of "operators".

3.	Fix variable-name typo in memory-barriers.txt.

4.	Replace ACCESS_ONCE() by READ_ONCE() and WRITE_ONCE().

5.	Call out smp_mb__after_unlock_lock() transitivity.  Most likely
	just in time to eliminate it entirely, mais c'est la vie!

							Thanx, Paul

------------------------------------------------------------------------

 b/Documentation/RCU/rcu_dereference.txt |    2 
 b/Documentation/kernel-parameters.txt   |   35 ++-
 b/Documentation/memory-barriers.txt     |  359 ++++++++++++++++----------------
 3 files changed, 209 insertions(+), 187 deletions(-)

--
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/