From: Greg KH <greg@kroah.com>
To: Donald Buczek <buczek@molgen.mpg.de>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
stable@vger.kernel.org, linux-nfs@vger.kernel.org,
bfields@fieldses.org
Subject: Re: [PATCH 4.14 0/2] Two nfsd4 fixes for 4.14 longterm
Date: Mon, 11 Feb 2019 14:34:41 +0100 [thread overview]
Message-ID: <20190211133441.GA17709@kroah.com> (raw)
In-Reply-To: <7a263d82-27e7-077f-3a51-78180785a41f@molgen.mpg.de>
On Tue, Feb 05, 2019 at 03:59:04PM +0100, Donald Buczek wrote:
> On 02/05/19 12:59, Salvatore Bonaccorso wrote:
>
> > Are you planning to submit the same as well for 4.9 LTS? The two
> > commits apply on top of 4.9.154 with line number updated.
>
> No, I'm not, because I didn't do any testing with 4.9.
>
> Additionally, I'm unsure about the right procedure for trivial backports
> to multiple trees: Individual patch sets, which apply perfectly, a single
> patch sets and Greg resolves that for the other trees or maybe no patch
> set at all and just a "please cherry-pick .... from upstream" mail.
The first patch in this series applies to 4.9.y, but the second does
not.
I'll be glad to take a backported, and tested, series, if someone still
cares about NFS for 4.9.y. But unless you really care about that tree,
I would not worry about it.
thanks,
greg k-h
next prev parent reply other threads:[~2019-02-11 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 10:01 [PATCH 4.14 0/2] Two nfsd4 fixes for 4.14 longterm Donald Buczek
2019-02-05 10:01 ` [PATCH 4.14 1/2] nfsd4: fix cached replies to solo SEQUENCE compounds Donald Buczek
2019-02-05 10:01 ` [PATCH 4.14 2/2] nfsd4: catch some false session retries Donald Buczek
2019-02-05 11:59 ` [PATCH 4.14 0/2] Two nfsd4 fixes for 4.14 longterm Salvatore Bonaccorso
2019-02-05 14:59 ` Donald Buczek
2019-02-11 13:34 ` Greg KH [this message]
2019-02-11 15:59 ` Salvatore Bonaccorso
2019-02-13 6:49 ` Salvatore Bonaccorso
2019-02-13 14:15 ` Greg KH
2019-02-05 21:31 ` J. Bruce Fields
2019-02-11 13:34 ` Greg KH
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=20190211133441.GA17709@kroah.com \
--to=greg@kroah.com \
--cc=bfields@fieldses.org \
--cc=buczek@molgen.mpg.de \
--cc=carnil@debian.org \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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.