From: Ian Kent <raven@themaw.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, neilb@suse.com,
stable@vger.kernel.org, tiwai@suse.de,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk
Subject: Re: FAILED: patch "[PATCH] autofs: use dentry flags to block walks during expire" failed to apply to 4.4-stable tree
Date: Tue, 27 Sep 2016 15:32:36 +0800 [thread overview]
Message-ID: <1474961556.32271.9.camel@themaw.net> (raw)
In-Reply-To: <20160927070559.GA4448@kroah.com>
On Tue, 2016-09-27 at 09:05 +0200, Greg KH wrote:
> On Tue, Sep 27, 2016 at 02:54:30PM +0800, Ian Kent wrote:
> > On Mon, 2016-09-26 at 09:56 +0200, gregkh@linuxfoundation.org wrote:
> >
> > Hi Greg,
> >
> > > The patch below does not apply to the 4.4-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 <stable@vgegr.kernel.org>.
> >
> > There is another bug fix from Al Viro upon which this path depends which has
> > not
> > been included in the stable tree.
> >
> > I recommend that I backport both patches.
> > Is that acceptable?
>
> Sure, or just give me the git commit id of the patch and I will queue it
> up as well before I apply this one.
There were some other changes to log prints as well, so they both need to be
back ported.
>
> > Should I include a cover description for the two patches explaining the need
> > for
> > the additional patch or just post the two patches to <
> > stable@vgegr.kernel.org>?
>
> Well, the correct address would be the good thing to use :)
LOL, oh, didn't notice that ...
>
> Other than that, either way is fine.
OK, I presume including the Linux tree commit id in each patch description is
sufficient, unless there's some specific format you need?
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2016-09-27 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 7:56 FAILED: patch "[PATCH] autofs: use dentry flags to block walks during expire" failed to apply to 4.4-stable tree gregkh
2016-09-27 6:54 ` Ian Kent
2016-09-27 7:05 ` Greg KH
2016-09-27 7:32 ` Ian Kent [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1474961556.32271.9.camel@themaw.net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=neilb@suse.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.