Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 20 Jul 2020 14:15:43 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     SeongJae Park <sjpark@amazon.com>
Cc:     sashal@kernel.org, stable@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: Upstream fixes not merged in 5.4.y
Message-ID: <20200720121543.GA2984743@kroah.com>
References: <20200629142805.28013-1-sjpark@amazon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200629142805.28013-1-sjpark@amazon.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.

thanks,

greg k-h