From: Michael Ellerman <michael@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org, stable@kernel.org
Subject: Re: [stable] [PATCH] powerpc/ptrace: Fix build with gcc 4.6
Date: Thu, 06 Dec 2012 17:58:24 +1100 [thread overview]
Message-ID: <1354777104.9974.5.camel@concordia> (raw)
In-Reply-To: <30738.1321497066@neuling.org>
On Thu, 2011-11-17 at 13:31 +1100, Michael Neuling wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>
> powerpc/ptrace: Fix build with gcc 4.6
>
> gcc (rightfully) complains that we are accessing beyond the
> end of the fpr array (we do, to access the fpscr).
This patch is still missing from the 3.0 stable series.
Do we need to resend ?
cheers
next prev parent reply other threads:[~2012-12-06 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 2:31 [stable] [PATCH] powerpc/ptrace: Fix build with gcc 4.6 Michael Neuling
2012-12-06 6:58 ` Michael Ellerman [this message]
2012-12-06 9:16 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2012-12-11 3:35 Michael Neuling
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=1354777104.9974.5.camel@concordia \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=stable@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).