From: hch@lst.de (Christoph Hellwig)
Subject: [PATCHv2] nvme: handle static ANA groups correctly
Date: Mon, 21 Jan 2019 14:49:52 +0100 [thread overview]
Message-ID: <20190121134952.GA25858@lst.de> (raw)
In-Reply-To: <01d7d14f-2ff8-737b-af4d-2a6444efc38d@grimberg.me>
On Mon, Jan 21, 2019@01:15:13AM -0800, Sagi Grimberg wrote:
> Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
>
> This seems like 5.1 material, anyone thinks this should
> go into 5.0?
Well, we underallocate a buffer without for a certain controller
feature set. I think we should merge Hannes' initial patch after
all which is a trivial two liner, and that seems spot on and safe
for 5.0.
prev parent reply other threads:[~2019-01-21 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 7:38 [PATCHv2] nvme: handle static ANA groups correctly Hannes Reinecke
2019-01-21 9:15 ` Sagi Grimberg
2019-01-21 13:49 ` Christoph Hellwig [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=20190121134952.GA25858@lst.de \
--to=hch@lst.de \
/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.