From: Leon Romanovsky <leon@kernel.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: linux-cifs@vger.kernel.org, smfrench@gmail.com,
senozhatsky@chromium.org, tom@talpey.com,
atteh.mailbox@gmail.com
Subject: Re: [PATCH] ksmbd: use ib_device_get_netdev() instead of calling ops.get_netdev
Date: Tue, 25 Mar 2025 14:22:50 +0200 [thread overview]
Message-ID: <20250325122250.GA11855@unreal> (raw)
In-Reply-To: <20250322003054.6500-1-linkinjeon@kernel.org>
On Sat, Mar 22, 2025 at 09:30:54AM +0900, Namjae Jeon wrote:
> ULPs are not supposed to call to ops.* directly.
>
> Suggested-by: Leon Romanovsky <leon@kernel.org>
> Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
> ---
> fs/smb/server/transport_rdma.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Thanks,
Reviewed-by: Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2025-03-25 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 0:30 [PATCH] ksmbd: use ib_device_get_netdev() instead of calling ops.get_netdev Namjae Jeon
2025-03-25 12:22 ` Leon Romanovsky [this message]
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=20250325122250.GA11855@unreal \
--to=leon@kernel.org \
--cc=atteh.mailbox@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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