[lkml]   [2013]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] remoteproc: properly fix missing CONFIG_FW_LOADER configurations
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? :)


greg k-h

 \ /
  Last update: 2013-03-06 02:01    [W:0.155 / U:0.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site