From: Peter Zijlstra <peterz@infradead.org>
To: mingo@kernel.org, hpa@zytor.com, jdike@addtoit.com,
linux-kernel@vger.kernel.org, richard@nod.at, tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/locking] x86, um: Add generic barrier.h
Date: Tue, 28 Jan 2014 20:30:57 +0100 [thread overview]
Message-ID: <20140128193057.GG11314@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <tip-rcmiqb07nyuhtsnmanxlj3il@git.kernel.org>
On Tue, Jan 28, 2014 at 11:25:12AM -0800, tip-bot for Peter Zijlstra wrote:
> Commit-ID: 673c36745c9f3100672853840b27e27638435e74
> Gitweb: http://git.kernel.org/tip/673c36745c9f3100672853840b27e27638435e74
> Author: Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Tue, 28 Jan 2014 15:12:36 +0100
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Tue, 28 Jan 2014 15:27:36 +0100
>
> x86, um: Add generic barrier.h
>
> It appears arch/um doesn't have any asm/barrier.h; cure this by
> including the generic one. Since UM is !SMP the defaults are good
> enough.
>
> ( The motivation are the latest MCS locking patches which use generic
> barriers. )
>
> Signed-off-by: Peter Zijlstra <peterz@infradead.org>
> Cc: Jeff Dike <jdike@addtoit.com>
> Cc: Richard Weinberger <richard@nod.at>
I just talked to rw on IRC and he pointed out that commit 9af2452
(already in Linus' tree) does the same.
prev parent reply other threads:[~2014-01-28 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 19:25 [tip:core/locking] x86, um: Add generic barrier.h tip-bot for Peter Zijlstra
2014-01-28 19:30 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140128193057.GG11314@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox