From: Steven Rostedt <rostedt@goodmis.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ahbong Chang <cwahbong@google.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Todd Poynor <toddpoynor@google.com>,
Philippe Ombredanne <pombredanne@nexb.com>
Subject: Re: [PATCH] trace: add missing forward declaration
Date: Wed, 18 Apr 2018 10:31:52 -0400 [thread overview]
Message-ID: <20180418103152.366b42c4@gandalf.local.home> (raw)
In-Reply-To: <20180417102909.GA8057@kroah.com>
On Tue, 17 Apr 2018 12:29:09 +0200
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Tue, Apr 17, 2018 at 02:18:47AM +0000, Ahbong Chang wrote:
> > It does not fail with any config without this fix. This is for new work.
>
> Then why not submit it as part of the "new work" patch series? That's
> how dependancies are normally handled.
I consider this patch making the kernel more robust. The reason I asked
was to know if it should be marked for stable or not. If nothing
currently relies on it, I just put it into the -rc as a "make the
kernel a little more robust" change. If other code relies on it, I
mark it for stable.
I'll take this patch as more of a clean up.
Thanks!
-- Steve
prev parent reply other threads:[~2018-04-18 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 2:36 [PATCH] trace: add missing forward declaration Ahbong Chang
2018-04-16 13:24 ` Steven Rostedt
2018-04-17 2:18 ` Ahbong Chang
2018-04-17 10:29 ` Greg Kroah-Hartman
2018-04-17 11:10 ` Ahbong Chang
2018-04-18 14:31 ` Steven Rostedt [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=20180418103152.366b42c4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=cwahbong@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=toddpoynor@google.com \
/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).