From: Bart Van Assche <bvanassche@acm.org>
To: Omar Sandoval <osandov@fb.com>
Cc: linux-block@vger.kernel.org, John Garry <john.garry@huawei.com>,
Don Brace <don.brace@microsemi.com>,
Douglas Gilbert <dgilbert@interlog.com>,
Jason Gunthorpe <jgg@nvidia.com>, Yi Zhang <yi.zhang@redhat.com>
Subject: Re: [PATCH blktests v2] rdma: Use rdma link instead of /sys/class/infiniband/*/parent
Date: Sun, 28 Mar 2021 16:41:55 -0700 [thread overview]
Message-ID: <ab74e069-15fb-f1d3-e5e5-fbec8989d14e@acm.org> (raw)
In-Reply-To: <20210328231210.3707-2-bvanassche@acm.org>
On 3/28/21 4:12 PM, Bart Van Assche wrote:
> The approach of verifying whether or not an RDMA interface is associated
> with the rdma_rxe interface by looking up its parent device is deprecated
> and will be removed soon from the Linux kernel. Hence this patch that uses
> the rdma link command instead.
Please ignore this patch - it has already been applied.
Bart.
next prev parent reply other threads:[~2021-03-28 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 23:12 [PATCH blktests] tests/block/031: Add a test for sharing a tag set across hardware queues Bart Van Assche
2021-03-28 23:12 ` [PATCH blktests v2] rdma: Use rdma link instead of /sys/class/infiniband/*/parent Bart Van Assche
2021-03-28 23:41 ` Bart Van Assche [this message]
2021-04-22 17:48 ` [PATCH blktests] tests/block/031: Add a test for sharing a tag set across hardware queues Omar Sandoval
-- strict thread matches above, loose matches on Subject: below --
2021-02-28 22:34 [PATCH blktests v2] rdma: Use rdma link instead of /sys/class/infiniband/*/parent Bart Van Assche
2021-03-07 20:40 ` Omar Sandoval
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=ab74e069-15fb-f1d3-e5e5-fbec8989d14e@acm.org \
--to=bvanassche@acm.org \
--cc=dgilbert@interlog.com \
--cc=don.brace@microsemi.com \
--cc=jgg@nvidia.com \
--cc=john.garry@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=yi.zhang@redhat.com \
/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).