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: <20140106101039.GD31570@twins.programming.kicks-ass.net>
Date:	Mon, 6 Jan 2014 11:10:39 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Krzysztof Hałasa <khalasa@...p.pl>,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>, Willy Tarreau <w@....eu>,
	Ingo Molnar <mingo@...nel.org>,
	Stephen Boyd <sboyd@...eaurora.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/2] seqlock: Use raw_ prefix instead of _no_lockdep

On Fri, Jan 03, 2014 at 04:28:31PM -0800, John Stultz wrote:
> On 01/02/2014 04:50 PM, Linus Torvalds wrote:
> > On Thu, Jan 2, 2014 at 3:11 PM, John Stultz <john.stultz@...aro.org> wrote:
> >> Linus disliked the _no_lockdep() naming, so instead
> >> use the more-consistent raw_* prefix to the non-lockdep
> >> enabled seqcount methods.
> >>
> >> This also adds raw_ methods for the write operations
> >> as well, which will be utilized in a following patch.
> > Ack on this and on 2/2. I'm assuming I'll get them through the -tip
> > tree, which is where the problem came from. No?
> 
> It seems Peter or Ingo are still on holiday. Hopefully they will be back
> on Monday to queue these.

Done! thanks!
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ