From: Ingo Molnar <mingo@elte.hu>
To: Pekka Paalanen <pq@iki.fi>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, hpa@zytor.com,
stuart@freedesktop.org, tglx@linutronix.de
Subject: Re: [tip:x86/urgent] x86: mmiotrace: quieten spurious warning message
Date: Wed, 1 Apr 2009 12:20:47 +0200 [thread overview]
Message-ID: <20090401102047.GA28574@elte.hu> (raw)
In-Reply-To: <20090326220338.1b4ad12e@daedalus.pq.iki.fi>
* Pekka Paalanen <pq@iki.fi> wrote:
> On Wed, 11 Mar 2009 20:45:45 GMT
> Stuart Bennett <stuart@freedesktop.org> wrote:
>
> > Commit-ID: afcfe024aebd74b0984a41af9a34e009cf5badaf
> > Gitweb: http://git.kernel.org/tip/afcfe024aebd74b0984a41af9a34e009cf5badaf
> > Author: "Stuart Bennett" <stuart@freedesktop.org>
> > AuthorDate: Wed, 11 Mar 2009 20:29:45 +0000
> > Commit: Ingo Molnar <mingo@elte.hu>
> > CommitDate: Wed, 11 Mar 2009 21:41:58 +0100
> >
> > x86: mmiotrace: quieten spurious warning message
> >
> > This message was being incorrectly emitted when using gdb,
> > so compile it out by default for now; there will be a
> > better fix in v2.6.30.
> >
> > Reported-by: Ingo Molnar <mingo@elte.hu>
> > Signed-off-by: Stuart Bennett <stuart@freedesktop.org>
> > Acked-by: Pekka Paalanen <pq@iki.fi>
> > Signed-off-by: Ingo Molnar <mingo@elte.hu>
> >
>
> Guys,
>
> wasn't this supposed to go into 2.6.29?
> I don't see this in Linus' master, was it too late?
Correct. There was no showstopper bug in the x86 tree
that necessiated a final post-rc8 push to Linus so this
did not get in.
We'll forward it to -stable once the tracing tree hits
upstream (this week). It could thus be part of .29.1.
Ingo
prev parent reply other threads:[~2009-04-01 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-afcfe024aebd74b0984a41af9a34e009cf5badaf@git.kernel.org>
2009-03-26 20:03 ` Pekka Paalanen
2009-04-01 10:20 ` Ingo Molnar [this message]
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=20090401102047.GA28574@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pq@iki.fi \
--cc=stuart@freedesktop.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®