From: Bart Van Assche <bvanassche@acm.org>
To: Laurence Oberman <loberman@redhat.com>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: Leon Romanovsky <leonro@mellanox.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] RDMA/srp: Accept again source addresses that do not have a port number
Date: Wed, 10 Apr 2019 08:50:34 -0700 [thread overview]
Message-ID: <1554911434.161891.23.camel@acm.org> (raw)
In-Reply-To: <bae975c8d5a4e256ba2987e5429b15333c1da0af.camel@redhat.com>
On Tue, 2019-03-26 at 11:37 -0400, Laurence Oberman wrote:
> This looks orrect to me, will test and report back.
Hi Laurence,
Although I know that you are busy: have you already had the time to test this
patch?
Thanks,
Bart.
next prev parent reply other threads:[~2019-04-10 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 20:34 [PATCH] RDMA/srp: Accept again source addresses that do not have a port number Bart Van Assche
2019-03-26 15:37 ` Laurence Oberman
2019-04-10 15:50 ` Bart Van Assche [this message]
2019-04-30 14:01 ` Bart Van Assche
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=1554911434.161891.23.camel@acm.org \
--to=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=stable@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 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).