From: Stefan Metzmacher <metze@samba.org>
To: David Howells <dhowells@redhat.com>, Steve French <sfrench@samba.org>
Cc: Paulo Alcantara <pc@manguebit.org>,
linux-cifs@vger.kernel.org,
Shyam Prasad N <sprasad@microsoft.com>,
Tom Talpey <tom@talpey.com>,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] cifs: Clean up declarations
Date: Fri, 12 Sep 2025 07:34:48 +0200 [thread overview]
Message-ID: <d3712068-ec74-4adb-9e1b-0f8cd6c39ad5@samba.org> (raw)
In-Reply-To: <20250904211839.1152340-3-dhowells@redhat.com>
Hi David,
can you please drop the changes to smbdirect.h?
(This is the only part I really looked at).
They leave strange comments around and will likely
cause conflicts with my current work.
Most or all functions will go soon anyway.
Thanks!
metze
> diff --git a/fs/smb/client/smbdirect.h b/fs/smb/client/smbdirect.h
> index e190cb96486f..6ed6d293824a 100644
> --- a/fs/smb/client/smbdirect.h
> +++ b/fs/smb/client/smbdirect.h
> @@ -114,18 +114,11 @@ struct smbd_connection {
> };
>
> /* Create a SMBDirect session */
> -struct smbd_connection *smbd_get_connection(
> - struct TCP_Server_Info *server, struct sockaddr *dstaddr);
>
> /* Reconnect SMBDirect session */
> -int smbd_reconnect(struct TCP_Server_Info *server);
> /* Destroy SMBDirect session */
> -void smbd_destroy(struct TCP_Server_Info *server);
>
> /* Interface for carrying upper layer I/O through send/recv */
> -int smbd_recv(struct smbd_connection *info, struct msghdr *msg);
> -int smbd_send(struct TCP_Server_Info *server,
> - int num_rqst, struct smb_rqst *rqst);
>
> enum mr_state {
> MR_READY,
> @@ -151,12 +144,22 @@ struct smbd_mr {
> };
>
> /* Interfaces to register and deregister MR for RDMA read/write */
> -struct smbd_mr *smbd_register_mr(
> - struct smbd_connection *info, struct iov_iter *iter,
> - bool writing, bool need_invalidate);
> -int smbd_deregister_mr(struct smbd_mr *mr);
>
> -/* PROTOTYPES */
> +
> +/*
> + * smbdirect.c
> + */
> +void smbd_destroy(struct TCP_Server_Info *server);
> +int smbd_reconnect(struct TCP_Server_Info *server);
> +struct smbd_connection *smbd_get_connection(
> + struct TCP_Server_Info *server, struct sockaddr *dstaddr);
> +int smbd_recv(struct smbd_connection *info, struct msghdr *msg);
> +int smbd_send(struct TCP_Server_Info *server,
> + int num_rqst, struct smb_rqst *rqst_array);
> +struct smbd_mr *smbd_register_mr(struct smbd_connection *info,
> + struct iov_iter *iter,
> + bool writing, bool need_invalidate);
> +int smbd_deregister_mr(struct smbd_mr *smbdirect_mr);
>
> #else
> #define cifs_rdma_enabled(server) 0
>
next prev parent reply other threads:[~2025-09-12 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 21:18 [RFC PATCH 0/2] cifs: Organise declarations in the cifs client header files David Howells
2025-09-04 21:18 ` [RFC PATCH 1/2] cifs: Do some preparation prior to organising the function declarations David Howells
2025-09-04 21:18 ` [RFC PATCH 2/2] cifs: Clean up declarations David Howells
2025-09-12 5:34 ` Stefan Metzmacher [this message]
2025-09-12 12:28 ` David Howells
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=d3712068-ec74-4adb-9e1b-0f8cd6c39ad5@samba.org \
--to=metze@samba.org \
--cc=dhowells@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=sfrench@samba.org \
--cc=sprasad@microsoft.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