All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhang.guodong@linux.dev
To: smfrench@gmail.com, linkinjeon@kernel.org, chenxiaosong@chenxiaosong.com
Cc: linux-cifs@vger.kernel.org, ZhangGuoDong <zhangguodong@kylinos.cn>
Subject: [PATCH v4 0/5] smb: move duplicate definitions into common header file, part 2
Date: Wed, 25 Feb 2026 04:10:55 +0000	[thread overview]
Message-ID: <20260225041100.707468-1-zhang.guodong@linux.dev> (raw)

From: ZhangGuoDong <zhangguodong@kylinos.cn>

v3->v4:
  - Patch #03: __le32  VolumeSerialNumber
  - Add patch #04

v3: https://lore.kernel.org/linux-cifs/20260216082018.156695-1-zhang.guodong@linux.dev/

v1: https://lore.kernel.org/all/20251209011020.3270989-1-chenxiaosong.chenxiaosong@linux.dev/
v2: https://lore.kernel.org/linux-cifs/20251211143228.172470-1-chenxiaosong.chenxiaosong@linux.dev/
The following patches from v1 and v2 have already been merged into mainline:
  - 94d5b8dbc5d9 smb: move some SMB1 definitions into common/smb1pdu.h
  - 2b6abb893e71 smb: move File Attributes definitions into common/fscc.h
  - c97503321ed3 smb: update struct duplicate_extents_to_file_ex
  - 2e0d224d8988 smb/server: add comment to FileSystemName of FileFsAttributeInformation
  - ab0347e67dac smb/client: remove DeviceType Flags and Device Characteristics definitions
  - 08c2a7d2bae9 smb: move file_notify_information to common/fscc.h
  - 6539e18517b6 smb: move SMB2 Notify Action Flags into common/smb2pdu.h
  - 9ec7629b430a smb: move notify completion filter flags into common/smb2pdu.h
  - bcdd6cfaf2ec smb: add documentation references for smb2 change notify definitions

This is a continuous effort to move duplicated definitions in both client
and server into common header files, which makes the code easier to maintain.

The previous work is here:
  - part 1: https://lore.kernel.org/linux-cifs/20251117112838.473051-1-chenxiaosong.chenxiaosong@linux.dev/

ZhangGuoDong (5):
  smb: move some definitions from common/smb2pdu.h into common/fscc.h
  smb: move file_basic_info into common/fscc.h
  smb: move filesystem_vol_info into common/fscc.h
  smb: update some doc references
  smb: introduce struct file_posix_info

 fs/smb/client/cifs_debug.c |   2 +-
 fs/smb/client/cifs_ioctl.h |   2 +-
 fs/smb/client/cifsfs.c     |   2 +-
 fs/smb/client/cifsglob.h   |   2 +-
 fs/smb/client/fscache.c    |   2 +-
 fs/smb/client/inode.c      |  22 +--
 fs/smb/client/readdir.c    |  28 +--
 fs/smb/client/reparse.h    |   4 +-
 fs/smb/client/smb1pdu.h    |   9 -
 fs/smb/client/smb2pdu.c    |   6 +-
 fs/smb/client/smb2pdu.h    |  22 +--
 fs/smb/common/fscc.h       | 379 ++++++++++++++++++++++++++++++++++++-
 fs/smb/common/smb2pdu.h    | 343 ---------------------------------
 fs/smb/server/smb2pdu.c    |  93 ++++-----
 fs/smb/server/smb2pdu.h    |  35 +---
 fs/smb/server/smb_common.h |   8 -
 16 files changed, 471 insertions(+), 488 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-02-25  4:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  4:10 zhang.guodong [this message]
2026-02-25  4:10 ` [PATCH v4 1/5] smb: move some definitions from common/smb2pdu.h into common/fscc.h zhang.guodong
2026-02-25  4:10 ` [PATCH v4 2/5] smb: move file_basic_info " zhang.guodong
2026-02-25  4:10 ` [PATCH v4 3/5] smb: move filesystem_vol_info " zhang.guodong
2026-02-27  2:37   ` Namjae Jeon
2026-02-27  2:48     ` ZhangGuoDong
2026-02-25  4:10 ` [PATCH v4 4/5] smb: update some doc references zhang.guodong
2026-03-01 17:41   ` Steve French
2026-02-25  4:11 ` [PATCH v4 5/5] smb: introduce struct file_posix_info zhang.guodong
2026-02-27  4:37   ` Namjae Jeon
2026-03-03  2:41     ` ZhangGuoDong
2026-03-03  3:00       ` ZhangGuoDong
2026-03-03  7:31         ` ChenXiaoSong
2026-03-03  8:58           ` ChenXiaoSong
2026-03-03  9:41             ` 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=20260225041100.707468-1-zhang.guodong@linux.dev \
    --to=zhang.guodong@linux.dev \
    --cc=chenxiaosong@chenxiaosong.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=zhangguodong@kylinos.cn \
    /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.