From: chenxiaosong@chenxiaosong.com
To: linkinjeon@kernel.org, sfrench@samba.org,
senozhatsky@chromium.org, tom@talpey.com,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
pc@manguebit.com, ronniesahlberg@gmail.com,
sprasad@microsoft.com, bharathsm@microsoft.com
Cc: chenxiaosong@kylinos.cn, liuzhengyuan@kylinos.cn,
huhai@kylinos.cn, liuyun01@kylinos.cn
Subject: [PATCH 0/2] smb: move SMB2 Status code to common header file
Date: Thu, 20 Jun 2024 09:34:34 +0000 [thread overview]
Message-ID: <20240620093436.411889-1-chenxiaosong@chenxiaosong.com> (raw)
From: ChenXiaoSong <chenxiaosong@kylinos.cn>
There are only slight differences between the client and server of SMB2
Status code definitions, in order to maintain the code more easily,
move all definitions to common header file.
ChenXiaoSong (2):
smb/client: fix typo to STATUS_MCA_OCCURRED
smb: move SMB2 Status code to common header file
fs/smb/client/smb2file.c | 2 +-
fs/smb/client/smb2inode.c | 2 +-
fs/smb/client/smb2maperror.c | 4 +-
fs/smb/client/smb2misc.c | 2 +-
fs/smb/client/smb2ops.c | 2 +-
fs/smb/client/smb2pdu.c | 2 +-
fs/smb/client/smb2transport.c | 2 +-
fs/smb/{client => common}/smb2status.h | 163 ++-
fs/smb/server/oplock.c | 2 +-
fs/smb/server/server.c | 2 +-
fs/smb/server/smb2misc.c | 2 +-
fs/smb/server/smb2pdu.c | 2 +-
fs/smb/server/smb_common.c | 2 +-
fs/smb/server/smbstatus.h | 1822 ------------------------
fs/smb/server/transport_rdma.c | 2 +-
15 files changed, 122 insertions(+), 1891 deletions(-)
rename fs/smb/{client => common}/smb2status.h (96%)
delete mode 100644 fs/smb/server/smbstatus.h
--
2.34.1
next reply other threads:[~2024-06-20 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 9:34 chenxiaosong [this message]
2024-06-20 9:34 ` [PATCH 1/2] smb/client: fix typo to STATUS_MCA_OCCURRED chenxiaosong
2024-06-20 9:34 ` [PATCH 2/2] smb: move SMB2 Status code to common header file chenxiaosong
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=20240620093436.411889-1-chenxiaosong@chenxiaosong.com \
--to=chenxiaosong@chenxiaosong.com \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@kylinos.cn \
--cc=huhai@kylinos.cn \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyun01@kylinos.cn \
--cc=liuzhengyuan@kylinos.cn \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®