From: Sagi Grimberg <sagi@grimberg.me>
To: Christoph Hellwig <hch@infradead.org>
Cc: netdev@vger.kernel.org, target-devel@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v1 3/4] nvme-rdma: use inet_pton_with_scope helper
Date: Tue, 28 Feb 2017 19:42:02 +0200 [thread overview]
Message-ID: <6b0d30df-371e-4108-83ee-c4e5886bedc2@grimberg.me> (raw)
In-Reply-To: <20170228163548.GC26480@infradead.org>
> Could use a proper changelog.
Will do, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH v1 3/4] nvme-rdma: use inet_pton_with_scope helper
Date: Tue, 28 Feb 2017 19:42:02 +0200 [thread overview]
Message-ID: <6b0d30df-371e-4108-83ee-c4e5886bedc2@grimberg.me> (raw)
In-Reply-To: <20170228163548.GC26480@infradead.org>
> Could use a proper changelog.
Will do, thanks!
next prev parent reply other threads:[~2017-02-28 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 17:39 [PATCH v1 0/4] Introduce a new helper for parsing ipv[4|6]:port to socket address Sagi Grimberg
2017-02-27 17:39 ` Sagi Grimberg
2017-02-27 17:39 ` [PATCH v1 1/4] net/utils: generic inet_pton_with_scope helper Sagi Grimberg
2017-02-27 17:39 ` Sagi Grimberg
2017-02-28 16:33 ` Christoph Hellwig
2017-02-28 16:33 ` Christoph Hellwig
2017-02-27 17:39 ` [PATCH v1 2/4] nvmet-rdma: use generic inet_pton_with_scope Sagi Grimberg
2017-02-27 17:39 ` Sagi Grimberg
2017-02-28 16:35 ` Christoph Hellwig
2017-02-28 16:35 ` Christoph Hellwig
2017-02-28 17:41 ` Sagi Grimberg
2017-02-28 17:41 ` Sagi Grimberg
2017-02-27 17:39 ` [PATCH v1 3/4] nvme-rdma: use inet_pton_with_scope helper Sagi Grimberg
2017-02-27 17:39 ` Sagi Grimberg
2017-02-28 16:35 ` Christoph Hellwig
2017-02-28 16:35 ` Christoph Hellwig
2017-02-28 17:42 ` Sagi Grimberg [this message]
2017-02-28 17:42 ` Sagi Grimberg
2017-02-27 17:39 ` [PATCH v1 4/4] iscsi-target: use generic inet_pton_with_scope Sagi Grimberg
2017-02-27 17:39 ` 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=6b0d30df-371e-4108-83ee-c4e5886bedc2@grimberg.me \
--to=sagi@grimberg.me \
--cc=hch@infradead.org \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
/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.