From: "Pali Rohár" <pali@kernel.org>
To: Steve French <sfrench@samba.org>,
Paulo Alcantara <pc@manguebit.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] cifs: Cleanup of duplicated structures
Date: Sun, 22 Dec 2024 18:24:01 +0100 [thread overview]
Message-ID: <20241222172404.24755-1-pali@kernel.org> (raw)
This patch series contains only code cleanup of few duplicates structures
and enums between smb/common and smb/client subdirs. No function change.
Can be useful also for ksmbd server part.
Pali Rohár (3):
cifs: Remove struct reparse_posix_data from struct cifs_open_info_data
cifs: Remove duplicate struct reparse_symlink_data and
SYMLINK_FLAG_RELATIVE
cifs: Rename struct reparse_posix_data to reparse_nfs_data_buffer and
move to common/smb2pdu.h
fs/smb/client/cifsglob.h | 5 +----
fs/smb/client/cifspdu.h | 30 ------------------------------
fs/smb/client/reparse.c | 15 +++++++--------
fs/smb/common/smb2pdu.h | 14 +++++++++++++-
4 files changed, 21 insertions(+), 43 deletions(-)
--
2.20.1
next reply other threads:[~2024-12-22 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 17:24 Pali Rohár [this message]
2024-12-22 17:24 ` [PATCH 1/3] cifs: Remove struct reparse_posix_data from struct cifs_open_info_data Pali Rohár
2024-12-22 17:24 ` [PATCH 2/3] cifs: Remove duplicate struct reparse_symlink_data and SYMLINK_FLAG_RELATIVE Pali Rohár
2024-12-22 17:24 ` [PATCH 3/3] cifs: Rename struct reparse_posix_data to reparse_nfs_data_buffer and move to common/smb2pdu.h Pali Rohár
2024-12-24 7:38 ` [PATCH 0/3] cifs: Cleanup of duplicated structures Namjae Jeon
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=20241222172404.24755-1-pali@kernel.org \
--to=pali@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.