submitting a patch for a stable tree

[greg@kroah.com (Greg KH)]

On Sun, Dec 17, 2017 at 09:23:45PM +0100, Greg KH wrote:
> On Sun, Dec 17, 2017 at 08:24:36PM +0100, Martin Kaiser wrote:
> > Dear all,
> > 
> > I tried to submit a patch for 4.14 that was already accepted upstream
> > and is in linux-next and the 4.15-rcs.
> > 
> > To understand how this should be done, I looked at
> > https://www.kernel.org/doc/html/v4.14/process/stable-kernel-rules.html
> > and tried to follow Option 2. It looks like I didn't get it right.
> > 
> > 
> > I started with a tree that contains the patch and ran
> > 
> > git format-patch -1 <commit id>
> > 
> > and then
> > 
> > git send-email --to stable at verg.kernel.org \
> >    --cc <the original maintainer and reviewers> \
> >    --annotate <patch file>
> > 
> > I added the upstream commit id above the original commit message and a
> > tag line
> > 
> > Cc: <stable@vger.kernel.org> # 4.14.x
> > 
> > to the patch and sent it out.
> 
> You did?  Was this on December 12:
> 	Subject: [PATCH] mfd: fsl-imx25: Clean up irq settings during removal
> ?
> 
> If so, I totally missed it (just now dug in my archives to find it.)

So I've now queued this up to 4.14.y and 4.9.y, does it need to go any
further back?

thanks,

greg k-h