From: Dave Hansen <dave@sr71.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] x86: perf: fix incorrect use of do_div() in nmi warning
Date: Fri, 12 Jul 2013 09:28:24 -0700 [thread overview]
Message-ID: <51E02EA8.9090700@sr71.net> (raw)
In-Reply-To: <20130712120843.GA21708@gmail.com>
On 07/12/2013 05:08 AM, Ingo Molnar wrote:
>> > Note, there was a second fix posted by Stephane Eranian for
>> > a separate patch which I also botched:
>> >
>> > http://lkml.kernel.org/r/20130704223010.GA30625@quad
>> >
>> > Both of these fixes need to get pulled in to Linus's tree and
>> > the 3.10 stable tree.
> This is a brand new v3.11 commit.
>
> It should not be included in any -stable tree, is it?
Ingo, you are correct. The commit only appeared in Linus's tree
post-3.10. It does not need to be in any stable trees.
next prev parent reply other threads:[~2013-07-12 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 21:44 [PATCH] x86: perf: fix incorrect use of do_div() in nmi warning Dave Hansen
2013-07-12 12:08 ` Ingo Molnar
2013-07-12 16:28 ` Dave Hansen [this message]
2013-07-12 13:30 ` [tip:perf/urgent] perf/x86: Fix incorrect use of do_div() in NMI warning tip-bot for Dave Hansen
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=51E02EA8.9090700@sr71.net \
--to=dave@sr71.net \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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