Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:56588 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751799AbdGYOFG (ORCPT ); Tue, 25 Jul 2017 10:05:06 -0400 Date: Tue, 25 Jul 2017 07:05:00 -0700 From: Greg KH To: "Maciej W. Rozycki" Cc: James Hogan , Ralf Baechle , stable@vger.kernel.org Subject: Re: FAILED: patch "[PATCH] MIPS: Rename `sigill_r6' to `sigill_r2r6' in" failed to apply to 3.18-stable tree Message-ID: <20170725140500.GF20317@kroah.com> References: <150095540311714@kroah.com> <20170725041009.GA32294@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Tue, Jul 25, 2017 at 11:31:31AM +0100, Maciej W. Rozycki wrote: > Hi Greg, > > > > The patch below does not apply to the 3.18-stable tree. > > > If someone wants it applied there, or to any other stable or longterm > > > tree, then please email the backport, including the original git commit > > > id to . > > > > Sorry, no, this doesn't belong in 3.18, as you said in the patch itself, > > sorry for the noise. > > One of the rejected patches does belong though, so how do I mark the > backport up correctly for you with the original commit ID and any other > information necessary for seamless processing? Just send it and say "this is commit id XXXX and needs to go to tree X.XX please" or something like that. The mailing list has tons of examples of this happening every day. thanks, greg k-h