linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH nvme-cli 0/4] Some useful fabrics patches
Date: Sun,  7 Aug 2016 15:19:21 +0300	[thread overview]
Message-ID: <1470572365-20674-1-git-send-email-sagi@grimberg.me> (raw)

Hey Keith,

So here are some useful fabrics patches I had in the pipe.
The first allows for ipv6 address resolution (resend) as
we will support it in fabrics for 4.9.

Patch 2 makes the discover output nice and pretty by outputing
human readable strings instead of numeric values.

Patch 3 just removes a redundant call.

Patch 4 is rfc, This was for my own convenience being too
lazy for manual parameterizing when discovering/connecting to nvmf
targets so this should allow to parameterize in a conf file.
Not sure if you are fond of the approach so I'd love to see some feedback.

Sagi Grimberg (4):
  fabrics: Allow ipv6 address resolution
  fabrics: stringify discover output.
  fabrics: Remove redundant build_options
  fabrics: Allow discover params to come from a conf file

 fabrics.c | 175 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++------
 1 file changed, 158 insertions(+), 17 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-08-07 12:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07 12:19 Sagi Grimberg [this message]
2016-08-07 12:19 ` [PATCH nvme-cli 1/4] fabrics: Allow ipv6 address resolution Sagi Grimberg
2016-08-08  6:55   ` Christoph Hellwig
2016-08-08 20:53     ` J Freyensee
2016-08-07 12:19 ` [PATCH nvme-cli 2/4] fabrics: stringify discover output Sagi Grimberg
2016-08-08  6:59   ` Christoph Hellwig
2016-08-08  8:41     ` Sagi Grimberg
2016-08-07 12:19 ` [PATCH nvme-cli 3/4] fabrics: Remove redundant build_options Sagi Grimberg
2016-08-08  7:01   ` Christoph Hellwig
2016-08-08  8:41     ` Sagi Grimberg
2016-08-07 12:19 ` [PATCH RFC nvme-cli 4/4] fabrics: Allow discover params to come from a conf file Sagi Grimberg
2016-08-08  7:03   ` Christoph Hellwig
2016-08-08  8:45     ` Sagi Grimberg
2016-08-08 21:13   ` J Freyensee
  -- strict thread matches above, loose matches on Subject: below --
2018-09-01  1:36 [PATCH nvme-cli 0/4] Some useful fabrics patches Sagi Grimberg
2018-09-06  0:20 ` Keith Busch

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=1470572365-20674-1-git-send-email-sagi@grimberg.me \
    --to=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;
as well as URLs for NNTP newsgroup(s).