From: SeongJae Park <sjpark@amazon.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: SeongJae Park <sjpark@amazon.com>, <sashal@kernel.org>,
<stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Re: Upstream fixes not merged in 5.4.y
Date: Mon, 20 Jul 2020 14:31:07 +0200 [thread overview]
Message-ID: <20200720123107.22001-1-sjpark@amazon.com> (raw)
In-Reply-To: <20200720121543.GA2984743@kroah.com>
On Mon, 20 Jul 2020 14:15:43 +0200 Greg KH <gregkh@linuxfoundation.org> wrote:
> On Mon, Jun 29, 2020 at 04:28:05PM +0200, SeongJae Park wrote:
> > Hello,
> >
> >
> > With my little script, I found below commits in the mainline tree are more than
> > 1 week old and fixing commits that back-ported in v5.4..v5.4.49, but not merged
> > in the stable/linux-5.4.y tree. Are those need to be merged in but missed or
> > dealyed?
> >
> > 9210c075cef2 ("nvme-pci: avoid race between nvme_reap_pending_cqes() and nvme_poll()")
>
> I tried this first patch, and it doesn't apply to the 5.4.y tree, so are
> you sure you tried these yourself?
>
> If so, please send a series of backported patches that you have
> successfully tested, or if a patch applies cleanly, just the git id.
Yes, I backported it on the latest 5.4.y before. I will rebase it on the
latest 5.4.y, test, and send the patch. Nonetheless, please note that it might
take some time (say, a couple of weeks?).
Thanks,
SeongJae Park
prev parent reply other threads:[~2020-07-20 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200629142805.28013-1-sjpark@amazon.com>
2020-06-29 16:15 ` Upstream fixes not merged in 5.4.y Greg KH
2020-06-30 6:29 ` SeongJae Park
2020-07-20 12:15 ` Greg KH
2020-07-20 12:31 ` SeongJae Park [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=20200720123107.22001-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@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 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).