From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Ohad Ben-Cohen <ohad@wizery.com>, stable <stable@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: properly fix missing CONFIG_FW_LOADER configurations
Date: Wed, 6 Mar 2013 08:46:09 +0800 [thread overview]
Message-ID: <20130306004609.GB28448@kroah.com> (raw)
In-Reply-To: <1362522169.16460.151.camel@x61.thuisdomein>
On Tue, Mar 05, 2013 at 11:22:49PM +0100, Paul Bolle wrote:
> On Wed, 2013-03-06 at 05:54 +0800, Greg KH wrote:
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> > for how to do this properly.
>
> 0) Actually I just copied the addresses included in commit
> e121aefa7d9f10eee5cf26ed47129237a05d940b upstream without really
> thinking.
>
> 1) But actually thinking about this: that upstream commit did end up in
> the (longterm) v3.4.y series. And my patch is also relevant for the
> v3.8.y series.
As that patch was in the 3.5-rc7 release, how can it be relevant for
3.8, or anything greater than 3.5 at all?
> Can't this patch, that fixes an obviously bogus commit,
> which was important enough for stable, be itself submitted with
> CC:stable?
How can you expect me to apply something that is already in the tree? :)
thanks,
greg k-h
next prev parent reply other threads:[~2013-03-06 0:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 19:20 Paul Bolle
2013-03-05 21:54 ` Greg KH
2013-03-05 22:22 ` Paul Bolle
2013-03-06 0:46 ` Greg KH [this message]
2013-03-06 7:53 ` Paul Bolle
2013-03-06 12:12 ` Greg KH
2013-03-06 12:32 ` Ohad Ben-Cohen
2013-03-06 12:38 ` Paul Bolle
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=20130306004609.GB28448@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=pebolle@tiscali.nl \
--cc=stable@vger.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
Powered by JetHome