From: Peter Zijlstra <peterz@infradead.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Waiman Long <Waiman.Long@hp.com>, Ingo Molnar <mingo@kernel.org>,
hpa@zytor.com, konrad.wilk@oracle.com,
torvalds@linux-foundation.org, davej@redhat.com, jeremy@goop.org,
paulmck@linux.vnet.ibm.com, raghavendra.kt@linux.vnet.ibm.com,
tglx@linutronix.de, oleg@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [tip:locking/core] x86, locking/rwlocks: Enable qrwlocks on x86
Date: Wed, 11 Jun 2014 10:59:21 +0200 [thread overview]
Message-ID: <20140611085921.GJ3213@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1402474451.3798.44.camel@x220>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
On Wed, Jun 11, 2014 at 10:14:11AM +0200, Paul Bolle wrote:
> On Fri, 2014-06-06 at 05:20 -0700, tip-bot for Waiman Long wrote:
> > +#if !defined(CONFIG_X86_OOSTORE) && !defined(CONFIG_X86_PPRO_FENCE)
>
> X86_OOSTORE was removed in v3.14, see commit 09df7c4c8097 ("x86: Remove
> CONFIG_X86_OOSTORE"). So the first test can be removed here, as it will
> always be true. Should I submit the trivial, but probably untested,
> patch to do that or do you prefer to do that yourself?
I was completely unaware of that removal. Yeah, I'll queue patch
removing this new instance of it.
Good to have it gone though, one little crazy less.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-06-11 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 13:12 [tip:locking/core] x86,locking: Enable qrwlock tip-bot for Waiman Long
2014-06-11 8:14 ` [tip:locking/core] x86, locking/rwlocks: Enable qrwlocks on x86 Paul Bolle
2014-06-11 8:59 ` Peter Zijlstra [this message]
2014-06-11 9:05 ` Peter Zijlstra
2014-06-19 12:36 ` [tip:locking/core] x86, locking: Use no more OOSTORE nonsense tip-bot for Peter Zijlstra
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=20140611085921.GJ3213@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Waiman.Long@hp.com \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pebolle@tiscali.nl \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome