linux-kernel - Re: [PATCH] remoteproc: properly fix missing CONFIG_FW

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1362522169.16460.151.camel@x61.thuisdomein>
Date:	Tue, 05 Mar 2013 23:22:49 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Ohad Ben-Cohen <ohad@...ery.com>, stable <stable@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] remoteproc: properly fix missing CONFIG_FW_LOADER
 configurations

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. Can't this patch, that fixes an obviously bogus commit,
which was important enough for stable, be itself submitted with
CC:stable?

Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/