From: Ben Hutchings <ben@decadent.org.uk>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] IA64: Export <asm/cmpxchg.h> to userland
Date: Fri, 08 Jun 2012 02:09:50 +0000 [thread overview]
Message-ID: <1339121390.21665.98.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <1339041112.21665.77.camel@deadeye.wl.decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
On Fri, 2012-06-08 at 10:43 +0900, Greg Kroah-Hartman wrote:
> On Thu, Jun 07, 2012 at 09:07:13PM +0100, Ben Hutchings wrote:
> > On Thu, Jun 07, 2012 at 04:54:56PM +0000, Luck, Tony wrote:
> > > > Parts of <asm/intrinsics.h> were moved to <asm/cmpxchg.h>, and the
> > > > former now includes the latter. The former is exported to userland
> > > > so the latter must be too.
> > >
> > > Already received and applied a patch that does this (though it added
> > > the cmpxchg.h a few lines earlier that you did).
> > >
> > > See commit: 98e4cff73
> > >
> > > It didn't get marked for stable though ... so if you need this to
> > > get pulled into the stable branches you'll need to poke Greg etc.
> > > manually.
> >
> > Greg, please cherry-pick commit
> > 85f8f7759e418c814ee2ceacf73eddb9bed39492 ('[IA64] Add cmpxchg.h to
> > exported userspace headers') for 3.4.y.
>
> I tried, but it doesn't apply properly. Can someone backport it and
> send it to me?
Sorry, I mean 98e4cff73a18af27f0d40d0b0d37f105dfc1994a; the former
commit is already in 3.4 and resulted in this breakage.
Ben.
--
Ben Hutchings
I haven't lost my mind; it's backed up on tape somewhere.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-06-08 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 3:51 [PATCH] IA64: Export <asm/cmpxchg.h> to userland Ben Hutchings
2012-06-07 16:54 ` Luck, Tony
2012-06-07 20:07 ` Ben Hutchings
2012-06-08 1:43 ` Greg Kroah-Hartman
2012-06-08 2:09 ` Ben Hutchings [this message]
2012-06-08 8:03 ` Greg Kroah-Hartman
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=1339121390.21665.98.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux-ia64@vger.kernel.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