From: Paul Bolle <pebolle@tiscali.nl>
To: Greg KH <gregkh@linuxfoundation.org>
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, 06 Mar 2013 08:53:22 +0100 [thread overview]
Message-ID: <1362556402.16460.158.camel@x61.thuisdomein> (raw)
In-Reply-To: <20130306004609.GB28448@kroah.com>
On Wed, 2013-03-06 at 08:46 +0800, Greg KH wrote:
> On Tue, Mar 05, 2013 at 11:22:49PM +0100, Paul Bolle wrote:
> > 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?
I seem to have confused you. My patch fixes a bug caused by a commit
that shipped in final release v3.5 (and is also part the 3.4.y series,
because that commit got added to that stable series).
> > 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? :)
It's not (yet) in the tree but fixes something that is in the tree.
Paul Bolle
next prev parent reply other threads:[~2013-03-06 7:53 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
2013-03-06 7:53 ` Paul Bolle [this message]
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=1362556402.16460.158.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ohad@wizery.com \
--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
all inboxes | Powered by JetHome®