From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmetcli: ANA configuration support
Date: Thu, 8 Nov 2018 09:48:50 +0100 [thread overview]
Message-ID: <20181108084850.GA3667@lst.de> (raw)
In-Reply-To: <20181017071118.GA23258@lst.de>
On Wed, Oct 17, 2018@09:11:18AM +0200, Christoph Hellwig wrote:
> On Sat, Oct 06, 2018@03:09:20PM +0200, Hannes Reinecke wrote:
> > > The new ANA code will probably need similar exception handling as the
> > > inline_data_size attribute.
> > >
> > Okay, will be fixing it up.
>
> Any chance to get a fixed version in the next days? I'd like to cut
> a new release with it not too long after the 4.19 release so that people
> can easily use the ANA code.
Do you still plan to resubmit this code?
next prev parent reply other threads:[~2018-11-08 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 11:08 [PATCH] nvmetcli: ANA configuration support Hannes Reinecke
2018-10-06 12:43 ` Christoph Hellwig
2018-10-06 13:09 ` Hannes Reinecke
2018-10-17 7:11 ` Christoph Hellwig
2018-11-08 8:48 ` Christoph Hellwig [this message]
2018-11-08 8:59 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2018-06-07 9:57 [PATCH nvmetcli] " Hannes Reinecke
2018-06-07 10:00 ` Johannes Thumshirn
2018-06-07 12:12 ` Christoph Hellwig
2018-06-07 12:38 ` Hannes Reinecke
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=20181108084850.GA3667@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 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).