From: Greg KH <gregkh@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, stable <stable@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>
Subject: Re: Commits missed for stable
Date: Tue, 11 Oct 2011 08:23:31 -0600 [thread overview]
Message-ID: <20111011142331.GA31776@suse.de> (raw)
In-Reply-To: <20111011142006.GA18281@suse.de>
On Tue, Oct 11, 2011 at 08:20:06AM -0600, Greg KH wrote:
> On Tue, Oct 11, 2011 at 08:45:38AM -0400, Steven Rostedt wrote:
> > It's come to my attention that a bug that was fixed by:
> >
> > 43dd61c9a09bd413e837df829e6bfb42159be52a
> > ftrace: Fix regression of :mod:module function enabling
Wait, that patch causes a TON of warnings to the build, so either I drop
it, or is there some other follow-on patch that I can apply to fix these
warnings?
greg k-h
next prev parent reply other threads:[~2011-10-11 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 12:45 Commits missed for stable Steven Rostedt
2011-10-11 14:20 ` Greg KH
2011-10-11 14:23 ` Greg KH [this message]
2011-10-11 14:24 ` Greg KH
2011-10-11 14:55 ` Steven Rostedt
2011-10-11 15:36 ` Greg KH
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=20111011142331.GA31776@suse.de \
--to=gregkh@suse.de \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@kernel.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