From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>
Subject: Fwd: move smbfsctl.h to common code (for the client)
Date: Thu, 9 Sep 2021 00:29:58 -0500 [thread overview]
Message-ID: <CAH2r5ms0qhzknr=iqnKMnVq9xT9-UDk9ZABX62PURSfM0__sTw@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5mvP49_fyCe-KHE3=DsTsxrJV707wSifReomUgfmh_4aBg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
---------- Forwarded message ---------
From: Steve French <smfrench@gmail.com>
Date: Thu, Sep 9, 2021 at 12:15 AM
Subject: move smbfsctl.h to common code (for the client)
To: Namjae Jeon <linkinjeon@kernel.org>, ronnie sahlberg
<ronniesahlberg@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
follow on patch can add it to the server, but this prepares for that
by adding the missing information to the larger/newer client version
of smbfsctl.h that was needed by the server (ksmbd) which uses an
older version of this header.
Also renames the fs/cifs_common ---> fs/smbfs_common
to be more consistent with the server (as we eventually rename fs/cifs
to fs/smbfs
in future releases) ... and try to use the name "cifs" less and "smb"
or "smbfs" more
for consistency.
--
Thanks,
Steve
--
Thanks,
Steve
[-- Attachment #2: 0003-cifs-move-SMB-FSCTL-definitions-to-common-code.patch --]
[-- Type: application/x-patch, Size: 1273 bytes --]
[-- Attachment #3: 0002-cifs-rename-cifs_common-to-smbfs_common.patch --]
[-- Type: application/x-patch, Size: 4899 bytes --]
[-- Attachment #4: 0001-cifs-update-FSCTL-definitions.patch --]
[-- Type: application/x-patch, Size: 2543 bytes --]
parent reply other threads:[~2021-09-09 5:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAH2r5mvP49_fyCe-KHE3=DsTsxrJV707wSifReomUgfmh_4aBg@mail.gmail.com>]
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='CAH2r5ms0qhzknr=iqnKMnVq9xT9-UDk9ZABX62PURSfM0__sTw@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.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 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).