From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, Christoph Lameter <cl@linux.com>
Subject: Re: powerpc: Replace __get_cpu_var uses
Date: Tue, 28 Oct 2014 14:51:59 +1100 [thread overview]
Message-ID: <1414468319.364.211.camel@pasglop> (raw)
In-Reply-To: <1414447475.1913.1.camel@concordia>
On Tue, 2014-10-28 at 09:04 +1100, Michael Ellerman wrote:
> On Tue, 2014-10-28 at 08:10 +1100, Benjamin Herrenschmidt wrote:
> > On Mon, 2014-10-27 at 10:57 -0500, Christoph Lameter wrote:
> > > Ping? We are planning to remove support for __get_cpu_var in the
> > > 3.19 merge period. I can move the definition for __get_cpu_var into the
> > > powerpc per cpu definition instead if we cannot get this merged?
> >
> > Yes, yes, I know, we should merge that, Michael, can you still throw
> > that in ?
>
> For 3.18, nah. We didn't even see it until after the merge window had closed.
No, we did see it a long time ago Michael, we just forgot about it. We
should put it in, everybody else has their equivalent.
> I realise they're all fairly simple translations, but it's too big and too easy
> for one of them to be wrong.
>
> I'm happy to put it in a topic branch for 3.19, or move the definition or
> whatever, your choice Christoph.
But then we'll have a tricky sync needed to make sure the removal of
__get_cpu_var() doesn't get into Linus tree before this. Unless we just
ack the whole lot and let Christoph carry it in the same branch where
the removal is.
Ben.
next prev parent reply other threads:[~2014-10-28 3:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 20:23 powerpc: Replace __get_cpu_var uses Christoph Lameter
2014-10-27 15:57 ` Christoph Lameter
2014-10-27 21:10 ` Benjamin Herrenschmidt
2014-10-27 22:04 ` Michael Ellerman
2014-10-28 2:31 ` Christoph Lameter
2014-10-28 3:51 ` Benjamin Herrenschmidt [this message]
2014-10-29 6:39 ` Michael Ellerman
2014-10-29 13:49 ` Christoph Lameter
2014-11-04 4:49 ` Michael Ellerman
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=1414468319.364.211.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).