Return-path: Received: from shards.monkeyblade.net ([198.137.202.13]:42502 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757166Ab2DLWOc (ORCPT ); Thu, 12 Apr 2012 18:14:32 -0400 Date: Thu, 12 Apr 2012 18:12:56 -0400 (EDT) Message-Id: <20120412.181256.1267592727086214582.davem@davemloft.net> (sfid-20120413_001448_349012_962E920F) To: felipe.contreras@gmail.com Cc: torvalds@linux-foundation.org, gregkh@linuxfoundation.org, lists@uece.net, linux-kernel@vger.kernel.org, stable@vger.kernel.org, akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk, linux-wireless@vger.kernel.org, c_manoha@qca.qualcomm.com, ath9k-devel@venema.h4ckr.net, linville@tuxdriver.com Subject: Re: [ 00/78] 3.3.2-stable review From: David Miller In-Reply-To: References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: From: Felipe Contreras Date: Fri, 13 Apr 2012 01:04:42 +0300 > Wrong is wrong, before or after the 3.3.1 tag, this patch is not > 'stable' material, and removing it does not affect upstream at all. What you don't understand is that bug fixes will get lost if you only fix them in -stable, it doesn't matter HOW THEY GOT into -stable. In fact IT HAS FUCKING HAPPENED that we didn't fix something upstream that got fixed in -stable a time long ago when we didn't have the policy we're using now which you're going so unreasonably ape-shit about. And we didn't notice the discrepency until much later. So the issues are real, there's proven precendence, and you're just so wrong it's not even funny.