mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jianchao.wang" <jianchao.w.wang@oracle.com>
To: Keith Busch <keith.busch@intel.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>,
	Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] nvme-pci: assign separate irq vectors for adminq and ioq0
Date: Tue, 13 Mar 2018 09:47:26 +0800	[thread overview]
Message-ID: <77263447-ffdd-ebe4-9cf9-8f0b2d9b2503@oracle.com> (raw)
In-Reply-To: <20180312185932.GH18494@localhost.localdomain>

Hi Keith

Thanks for your precious time for testing and reviewing.
I will send out V3 next.

Sincerely
Jianchao

On 03/13/2018 02:59 AM, Keith Busch wrote:
> Hi Jianchao,
> 
> The patch tests fine on all hardware I had. I'd like to queue this up
> for the next 4.16-rc. Could you send a v3 with the cleanup changes Andy
> suggested and a changelog aligned with Ming's insights?
> 
> Thanks,
> Keith
> 

  reply	other threads:[~2018-03-13  1:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 15:48 Jianchao Wang
2018-02-28 15:59 ` Andy Shevchenko
2018-03-02  3:06   ` jianchao.wang
2018-03-12 18:59     ` Keith Busch
2018-03-13  1:47       ` jianchao.wang [this message]
2018-02-28 16:47 ` Christoph Hellwig
2018-03-01  9:28   ` Sagi Grimberg
2018-03-01 10:05     ` jianchao.wang
2018-03-01 15:15       ` Keith Busch
2018-03-02  3:11         ` jianchao.wang
2018-03-01 15:03   ` Ming Lei
2018-03-01 16:10     ` Keith Busch
2018-03-08  7:42       ` Christoph Hellwig
2018-03-09 17:24         ` Keith Busch
2018-03-12  9:09           ` Ming Lei
2018-03-02  3:18   ` jianchao.wang

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=77263447-ffdd-ebe4-9cf9-8f0b2d9b2503@oracle.com \
    --to=jianchao.w.wang@oracle.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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
Powered by JetHome