From: Bjorn Helgaas <helgaas@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, Jens Axboe <axboe@fb.com>,
stable@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
Jian-Hong Pan <jian-hong@endlessm.com>,
linux@endlessm.com
Subject: Re: [PATCH v2] Revert "nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T"
Date: Fri, 1 Nov 2019 17:44:16 -0500 [thread overview]
Message-ID: <20191101224416.GA225762@google.com> (raw)
In-Reply-To: <20191031133028.GA4617@lst.de>
On Thu, Oct 31, 2019 at 02:30:28PM +0100, Christoph Hellwig wrote:
> On Thu, Oct 31, 2019 at 08:28:53AM -0500, Bjorn Helgaas wrote:
> > On Thu, Oct 31, 2019 at 05:34:09PM +0800, Jian-Hong Pan wrote:
> > > Since commit 253eaf4faaaa ("PCI/MSI: Fix incorrect MSI-X masking on
> > > resume") is merged, we can revert the previous quirk now.
> >
> > 253eaf4faaaa is pending on my pci/msi branch, planned to be merged
> > during the v5.5 merge window.
> >
> > This revert patch must not be merged before 253eaf4faaaa. The easiest
> > way to do that would be for me to merge this one as well; otherwise
> > we have to try to make things happen in the right order during the
> > merge window.
> >
> > If the NVMe folks ack this idea and the patch, I'd be happy to merge
> > it.
>
> Fine with me.
>
> Acked-by: Christoph Hellwig <hch@lst.de>
OK, I'll ask Linus to merge this revert after my main PCI pull request
for v5.5-rc1.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-11-01 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 9:34 [PATCH v2] Revert "nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T" Jian-Hong Pan
2019-10-31 13:28 ` Bjorn Helgaas
2019-10-31 13:30 ` Christoph Hellwig
2019-11-01 22:44 ` Bjorn Helgaas [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=20191101224416.GA225762@google.com \
--to=helgaas@kernel.org \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jian-hong@endlessm.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=sagi@grimberg.me \
--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).