From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com ([66.111.4.27]:46420 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751723AbcAXVnH (ORCPT ); Sun, 24 Jan 2016 16:43:07 -0500 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 93CC4201F8 for ; Sun, 24 Jan 2016 16:43:06 -0500 (EST) Date: Sun, 24 Jan 2016 13:43:05 -0800 From: Greg KH To: Michael Ellerman Cc: stable@vger.kernel.org, alistair@popple.id.au Subject: Re: Please do NOT backport commit 25642e1459ac ("powerpc/opal-irqchip: Fix double endian conversion") Message-ID: <20160124214305.GC9841@kroah.com> References: <1450685649.7418.4.camel@ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1450685649.7418.4.camel@ellerman.id.au> Sender: stable-owner@vger.kernel.org List-ID: On Mon, Dec 21, 2015 at 07:14:09PM +1100, Michael Ellerman wrote: > Hi stable folks, > > Please do not backport commit 25642e1459ac ("powerpc/opal-irqchip: Fix double > endian conversion"). > > It fixed one bug but added another :/ > > We've fixed it upstream with an additional commit, but will send a combined > patch for stable. > > I couldn't see any documentation on how to request that a commit is not > backported once it's already tagged in the change log, let me know if there's > a way I can do it that makes it easier for you guys. I'd rather take the original patches, and not rely on some combined patch, as that will differ from upstream. So can I just take this patch now and you tell me what the other commit is that I need to keep a bug from happening? thanks, greg k-h