From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: trond.myklebust@hammerspace.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] NFS: Ensure O_DIRECT reports an error if the bytes" failed to apply to 4.19-stable tree
Date: Tue, 3 Sep 2019 17:22:10 -0400 [thread overview]
Message-ID: <20190903212210.GR5281@sasha-vm> (raw)
In-Reply-To: <156753715823987@kroah.com>
On Tue, Sep 03, 2019 at 08:59:18PM +0200, gregkh@linuxfoundation.org wrote:
>The patch below does not apply to the 4.19-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@vger.kernel.org>.
I've fixed it up and queued it for 4.19, 4.14, 4.9, and 4.4. I took
df3accb849607 ("NFS: Pass error information to the pgio error cleanup
routine") to make the backport cleaner.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-09-03 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 18:59 FAILED: patch "[PATCH] NFS: Ensure O_DIRECT reports an error if the bytes" failed to apply to 4.19-stable tree gregkh
2019-09-03 21:22 ` Sasha Levin [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=20190903212210.GR5281@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).