From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 12 Jul 2013 13:57:18 -0400 From: Theodore Ts'o To: Greg Kroah-Hartman Cc: "H. Peter Anvin" , "John W. Linville" , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, stable@vger.kernel.org, ksummit-2013-discuss@lists.linux-foundation.org Subject: Re: [Ksummit-2013-discuss] When to push bug fixes to mainline Message-ID: <20130712175718.GA342@thunk.org> References: <20130711214830.611455274@linuxfoundation.org> <20130712005023.GB31005@thunk.org> <20130712025745.GA24086@tuxdriver.com> <20130712033430.GA3798@kroah.com> <51E03AEE.5010403@zytor.com> <20130712172836.GA7627@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130712172836.GA7627@kroah.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: On Fri, Jul 12, 2013 at 10:28:36AM -0700, Greg Kroah-Hartman wrote: > On Fri, Jul 12, 2013 at 10:20:46AM -0700, H. Peter Anvin wrote: > > On the subject of the stable tree: could we get a standard format for > > requesting post-inclusion elevation of patches to stable status? It > > isn't all that unusual that the need for -stable is highlighted after a > > patch has been included in a maintainer's tree, and rebasing to add > > stable metadata annoys Linus. > > After it's in Linus's tree, just send the git id of the patch to > stable@vger.kernel.org, along with what stable tree(s) you want to see > the patch backported to. > > Documentation/stable_kernel_rules.txt should be pretty explicit about > how to do this, but if not, patches to it are always welcome. FWIW, Documentation/stable_kernel_rules.txt currently says that you should send the patch. I checked to see whether sending the git id was sufficient, and upon reading stable_kernel_rules.txt, decided to simply run git format-patch/git send-email of the commits in mainline. Apparently no one seemed to mind.... - Ted