From: Leon Romanovsky <leonro@nvidia.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, <linux-rdma@vger.kernel.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: [PATCH 1/3] ib_srp: Add more documentation
Date: Wed, 16 Feb 2022 09:02:23 +0200 [thread overview]
Message-ID: <Ygyhf1YU6mJoVubK@unreal> (raw)
In-Reply-To: <d76031cc-29bb-5dad-6f30-b69fee5966cb@acm.org>
On Tue, Feb 15, 2022 at 12:34:27PM -0800, Bart Van Assche wrote:
> On 2/15/22 10:42, Leon Romanovsky wrote:
> > On Tue, Feb 15, 2022 at 10:26:48AM -0800, Bart Van Assche wrote:
> > > /*
> > > + * RDMA adapter in the initiator system.
> > > + *
> > > + * @dev_list: List of RDMA ports associated with this RDMA adapter (srp_host).
> >
> > Isn't this list of RDMA devices and not ports?
>
> Please take a look at srp_add_port(). I think that function establishes a
> 1:1 relationship between an RDMA port and struct srp_host.
Right, but this list contains devices and not ports.
Anyway, it is not important.
Thanks
>
> Thanks,
>
> Bart.
>
next prev parent reply other threads:[~2022-02-16 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 18:26 [PATCH 0/3] Fix a deadlock in the ib_srp driver Bart Van Assche
2022-02-15 18:26 ` [PATCH 1/3] ib_srp: Add more documentation Bart Van Assche
2022-02-15 18:42 ` Leon Romanovsky
2022-02-15 20:34 ` Bart Van Assche
2022-02-16 7:02 ` Leon Romanovsky [this message]
2022-02-15 18:26 ` [PATCH 2/3] ib_srp: Protect the target list with a mutex instead of a spinlock Bart Van Assche
2022-02-15 18:44 ` Leon Romanovsky
2022-02-15 20:35 ` Bart Van Assche
2022-02-15 18:26 ` [PATCH 3/3] ib_srp: Fix a deadlock Bart Van Assche
2022-02-15 18:51 ` Leon Romanovsky
2022-02-15 20:37 ` Bart Van Assche
2022-02-15 20:41 ` Jason Gunthorpe
2022-02-15 20:50 ` 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=Ygyhf1YU6mJoVubK@unreal \
--to=leonro@nvidia.com \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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