linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Reitmayr <treitmayr@devbase.at>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	leigh123linux@googlemail.com, Dave Jones <davej@redhat.com>
Subject: Re: [PATCH] Use correct byte-sized register constraint in __xchg_op()
Date: Thu, 05 Apr 2012 23:16:03 +0200	[thread overview]
Message-ID: <1333660563.8861.3.camel@localhost> (raw)
In-Reply-To: <CA+5PVA50Bz2BtDw77yBvQpc9BxGZqyp0_4JeZUY-E_QB0mFZsA@mail.gmail.com>

Hi Josh,
You are right, this bug also affects 3.3 and IMO should be fixed there,
too!
-Thomas

Am Donnerstag, den 05.04.2012, 16:27 -0400 schrieb Josh Boyer:
> On Tue, Apr 3, 2012 at 8:37 PM, Josh Boyer <jwboyer@gmail.com> wrote:
> > On Mon, Apr 2, 2012 at 7:15 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> >> x86-64 can access the low half of any register, but i386 can only do
> >> it with a subset of registers.  'r' causes compilation failures on i386,
> >> but 'q' expresses the constraint properly.
> >>
> >> Signed-off-by: Jeremy Fitzhardinge <jeremy@goop.org>
> >> Reported-by: Leigh Scott <leigh123linux@googlemail.com>
> >> Tested-by: Thomas Reitmayr <treitmayr@devbase.at>
> >
> > This should be CC'd to stable, given the bug shows up in 3.3, right?
> 
> Er.. this patch seems to have been lost in limbo.  Is anyone following
> up on it?
> 
> josh
> 



  reply	other threads:[~2012-04-05 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 23:15 [PATCH] Use correct byte-sized register constraint in __xchg_op() Jeremy Fitzhardinge
2012-04-04  0:37 ` Josh Boyer
2012-04-05 20:27   ` Josh Boyer
2012-04-05 21:16     ` Thomas Reitmayr [this message]
2012-04-06  7:46 ` Jeremy Fitzhardinge
2012-04-06 16:52 ` [tip:x86/urgent] x86: " tip-bot for Jeremy Fitzhardinge
2012-04-06 16:53 ` [tip:x86/urgent] x86: Use correct byte-sized register constraint in __add() tip-bot for H. Peter Anvin

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=1333660563.8861.3.camel@localhost \
    --to=treitmayr@devbase.at \
    --cc=davej@redhat.com \
    --cc=jeremy@goop.org \
    --cc=jwboyer@gmail.com \
    --cc=leigh123linux@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).