From: Ronnie Sahlberg <lsahlber@redhat.com>
To: linux-cifs <linux-cifs@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>
Subject: [PATCH 0/3] cifs: create a common smb2pdu.h for client and server
Date: Fri, 3 Sep 2021 09:37:13 +1000 [thread overview]
Message-ID: <20210902233716.1923306-1-lsahlber@redhat.com> (raw)
Steve,
Here is an initial set of patches that starts moving SMB2 PDU definitions
from the client/server into a shared smb2pd.h file.
It moves the command opcode values into cifs_common,
it renames cifs smb2_sync_hdr to smb2_hdr to harmonize with ksmbd naming
and it moves the tree connect and disconnect PDU definitions to the shared
file.
next reply other threads:[~2021-09-02 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 23:37 Ronnie Sahlberg [this message]
2021-09-02 23:37 ` [PATCH 1/3] cifs: create smb2pdu.h to be shared between cifs client and server Ronnie Sahlberg
2021-09-02 23:37 ` [PATCH 2/3] cifs: rename smb2_sync_hdr to smb2_hdr to harmonize naming with ksmbd Ronnie Sahlberg
2021-09-02 23:37 ` [PATCH 3/3] cifs: move smb2 tree_[dis]connect definitions to the shared cifs_common Ronnie Sahlberg
2021-09-03 0:00 ` [PATCH 0/3] cifs: create a common smb2pdu.h for client and server Steve French
2021-09-03 3:01 ` ronnie sahlberg
2021-09-03 16:53 ` Steve French
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=20210902233716.1923306-1-lsahlber@redhat.com \
--to=lsahlber@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.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