From: David Miller <davem@davemloft.net>
To: sagi@grimberg.me
Cc: linux-nvme@lists.infradead.org, netdev@vger.kernel.org,
hch@lst.de, axboe@fb.com
Subject: Re: [PATCH v3 0/4] Introduce a new helper for parsing ipv[4|6]:port to socket address
Date: Wed, 29 Mar 2017 10:16:17 -0700 (PDT) [thread overview]
Message-ID: <20170329.101617.2078695643478702071.davem@davemloft.net> (raw)
In-Reply-To: <a484e88e-317c-42a6-f7c2-69b77cb8486a@grimberg.me>
From: Sagi Grimberg <sagi@grimberg.me>
Date: Wed, 29 Mar 2017 19:50:51 +0300
>
>>> Hi Dave,
>>>
>>> This set got review tags from two kernel maintainers but this is your
>>> realm so I wouldn't be comfortable moving forward with this without
>>> your feedback.
>>
>> Would it be possible to get a review from one of the netdev folks
>> on patch 1/4?
>
> Hi everyone,
>
> Still no feedback...
>
> This patchset is targeted to 4.12 as it adds IPv6 support to
> nvme over fabrics drivers which is desired by some linux users.
Please repost, the problem was you mixed it in a series that was
not targetting the net tree, so it was confusing what was going on.
Just submit the networking change, by itself, for review.
Thank you.
next prev parent reply other threads:[~2017-03-29 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 12:49 [PATCH v3 0/4] Introduce a new helper for parsing ipv[4|6]:port to socket address Sagi Grimberg
2017-03-09 12:49 ` [PATCH v3 1/4] net/utils: generic inet_pton_with_scope helper Sagi Grimberg
2017-03-09 12:49 ` [PATCH v3 2/4] nvmet-rdma: use generic inet_pton_with_scope Sagi Grimberg
2017-03-09 12:49 ` [PATCH v3 3/4] nvme-rdma: use inet_pton_with_scope helper Sagi Grimberg
2017-03-09 12:49 ` [PATCH v3 4/4] iscsi-target: use generic inet_pton_with_scope Sagi Grimberg
2017-03-13 14:00 ` [PATCH v3 0/4] Introduce a new helper for parsing ipv[4|6]:port to socket address Sagi Grimberg
2017-03-19 16:12 ` Sagi Grimberg
2017-03-29 16:50 ` Sagi Grimberg
2017-03-29 17:16 ` David Miller [this message]
2017-03-29 17:22 ` Sagi Grimberg
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=20170329.101617.2078695643478702071.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).