From: Christoph Hellwig <hch@lst.de>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
Jens Axboe <axboe@fb.com>, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/2] nvme-pic: improve max I/O queue handling
Date: Fri, 13 Nov 2020 17:25:02 +0100 [thread overview]
Message-ID: <20201113162502.GA16940@lst.de> (raw)
In-Reply-To: <c753af20-878a-91ad-c5c2-692016fe2014@linux.ibm.com>
On Fri, Nov 13, 2020 at 02:15:59PM +0100, Niklas Schnelle wrote:
>
>
> On 11/12/20 6:36 PM, Keith Busch wrote:
> > On Thu, Nov 12, 2020 at 04:45:35PM +0100, Niklas Schnelle wrote:
> >> You got to get something wrong, I hope in this case it's just the subject
> >> of the cover letter :D
> >
> > I suppose the change logs could be worded a little better :)
>
> Do you think I should send a v2 with an improved message?
> I just realized I'm pretty alone (and wrong) in starting
> the commit message body lower case too.
I'll pull in soon, no need to resend.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH 0/2] nvme-pic: improve max I/O queue handling
Date: Fri, 13 Nov 2020 17:25:02 +0100 [thread overview]
Message-ID: <20201113162502.GA16940@lst.de> (raw)
In-Reply-To: <c753af20-878a-91ad-c5c2-692016fe2014@linux.ibm.com>
On Fri, Nov 13, 2020 at 02:15:59PM +0100, Niklas Schnelle wrote:
>
>
> On 11/12/20 6:36 PM, Keith Busch wrote:
> > On Thu, Nov 12, 2020 at 04:45:35PM +0100, Niklas Schnelle wrote:
> >> You got to get something wrong, I hope in this case it's just the subject
> >> of the cover letter :D
> >
> > I suppose the change logs could be worded a little better :)
>
> Do you think I should send a v2 with an improved message?
> I just realized I'm pretty alone (and wrong) in starting
> the commit message body lower case too.
I'll pull in soon, no need to resend.
next prev parent reply other threads:[~2020-11-13 16:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 8:23 [PATCH 0/2] nvme-pic: improve max I/O queue handling Niklas Schnelle
2020-11-12 8:23 ` Niklas Schnelle
2020-11-12 8:23 ` [PATCH 1/2] nvme-pci: drop min() from nr_io_queues assignment Niklas Schnelle
2020-11-12 8:23 ` Niklas Schnelle
2020-11-14 9:06 ` Christoph Hellwig
2020-11-14 9:06 ` Christoph Hellwig
2020-11-12 8:23 ` [PATCH 2/2] nvme-pci: don't allocate unused I/O queues Niklas Schnelle
2020-11-12 8:23 ` Niklas Schnelle
2020-11-12 14:53 ` [PATCH 0/2] nvme-pic: improve max I/O queue handling Keith Busch
2020-11-12 14:53 ` Keith Busch
2020-11-12 15:45 ` Niklas Schnelle
2020-11-12 15:45 ` Niklas Schnelle
2020-11-12 17:36 ` Keith Busch
2020-11-12 17:36 ` Keith Busch
2020-11-13 13:15 ` Niklas Schnelle
2020-11-13 13:15 ` Niklas Schnelle
2020-11-13 16:25 ` Christoph Hellwig [this message]
2020-11-13 16:25 ` Christoph Hellwig
2020-11-13 16:52 ` Niklas Schnelle
2020-11-13 16:52 ` Niklas Schnelle
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=20201113162502.GA16940@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=schnelle@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.