From: Ronnie Sahlberg <lsahlber@redhat.com>
To: linux-cifs <linux-cifs@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>
Subject: [PATCH 0/4] Start moving common cifs/ksmbd definitions into a common directory
Date: Tue, 7 Sep 2021 08:46:44 +1000 [thread overview]
Message-ID: <20210906224648.2062040-1-lsahlber@redhat.com> (raw)
Steve, Namjae,
Here is a start of work to share common definitions between the cifs client and the server.
The patches build ontop of Namjaes patch to rework the smb2_hdr structure
that he recently sent to the list.
It creates a new shared smb2pdu.h file and starts moving definitions over.
The two copies of smb2pdu.h, in cifs/ and ksmbd/ have diverged a bit
so some things are being renamed in these patches.
NegotiateProtocol is in two separate patches since for this funciton the
changes are a little more than just renames, for example I change several
arrays at the tail of structures from [number] to simply []
so that needs careful review.
Two patches are for cifs and cifs_common and two patches are for ksmbd.
The ksmbd patches depend on the cifs patches so the cifs patches have to go in first.
next reply other threads:[~2021-09-06 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 22:46 Ronnie Sahlberg [this message]
2021-09-06 22:46 ` [PATCH 1/4] cifs: Create a new shared file holding smb2 pdu definitions Ronnie Sahlberg
2021-09-06 22:46 ` [PATCH 2/4] ksmbd: switch to use shared definitions where available Ronnie Sahlberg
2021-09-06 22:46 ` [PATCH 3/4] cifs: move NEGOTIATE_PROTOCOL definitions out into the common area Ronnie Sahlberg
2021-09-06 22:46 ` [PATCH 4/4] ksmbd: use the common definitions for NEGOTIATE_PROTOCOL Ronnie Sahlberg
2021-09-07 1:03 ` [PATCH 0/4] Start moving common cifs/ksmbd definitions into a common directory Namjae Jeon
2021-09-07 2:57 ` ronnie sahlberg
2021-09-07 3:01 ` Steve French
2021-09-07 8:40 ` 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=20210906224648.2062040-1-lsahlber@redhat.com \
--to=lsahlber@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.com \
--subject='Re: [PATCH 0/4] Start moving common cifs/ksmbd definitions into a common directory' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).