From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
linuxppc-dev@ozlabs.org, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] powerpc/perf_event: Fix oops due to perf_event_do_pending call
Date: Wed, 14 Apr 2010 16:53:16 +1000 [thread overview]
Message-ID: <1271227996.13059.138.camel@pasglop> (raw)
In-Reply-To: <20100414064603.GA4714@drongo>
On Wed, 2010-04-14 at 16:46 +1000, Paul Mackerras wrote:
> Ben, please put this in your tree of fixes to go to Linus for 2.6.34,
> since it fixes a potential panic.
Should it go to -stable as well ? How far back ?
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] powerpc/perf_event: Fix oops due to perf_event_do_pending call
Date: Wed, 14 Apr 2010 16:53:16 +1000 [thread overview]
Message-ID: <1271227996.13059.138.camel@pasglop> (raw)
In-Reply-To: <20100414064603.GA4714@drongo>
On Wed, 2010-04-14 at 16:46 +1000, Paul Mackerras wrote:
> Ben, please put this in your tree of fixes to go to Linus for 2.6.34,
> since it fixes a potential panic.
Should it go to -stable as well ? How far back ?
Cheers,
Ben.
next prev parent reply other threads:[~2010-04-14 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 6:46 [PATCH] powerpc/perf_event: Fix oops due to perf_event_do_pending call Paul Mackerras
2010-04-14 6:46 ` Paul Mackerras
2010-04-14 6:53 ` Benjamin Herrenschmidt [this message]
2010-04-14 6:53 ` Benjamin Herrenschmidt
2010-04-14 12:11 ` Michael Ellerman
2010-04-14 12:11 ` 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=1271227996.13059.138.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.