From: ZhangGuoDong <zhang.guodong@linux.dev>
To: linkinjeon@kernel.org, pc@manguebit.org
Cc: linux-cifs@vger.kernel.org,
ZhangGuoDong <zhangguodong@kylinos.cn>,
ChenXiaoSong <chenxiaosong@kylinos.cn>
Subject: [PATCH 3/3] smb/common: update POSIX extension specification references
Date: Sun, 20 Sep 2026 13:56:53 +0800 [thread overview]
Message-ID: <20260920055653.114794-4-zhang.guodong@linux.dev> (raw)
In-Reply-To: <20260920055653.114794-1-zhang.guodong@linux.dev>
From: ZhangGuoDong <zhangguodong@kylinos.cn>
The POSIX extension specifications have now been published:
https://smb3posix.org/
Suggested-by: Paulo Alcantara <pc@manguebit.org>
Reviewed-by: ChenXiaoSong <chenxiaosong@kylinos.cn>
Signed-off-by: ZhangGuoDong <zhangguodong@kylinos.cn>
---
fs/smb/common/fscc.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/smb/common/fscc.h b/fs/smb/common/fscc.h
index e46d3379b779..61bb1f8e4a64 100644
--- a/fs/smb/common/fscc.h
+++ b/fs/smb/common/fscc.h
@@ -575,8 +575,7 @@ struct file_notify_information {
} __packed;
/*
- * See POSIX Extensions to MS-FSCC 2.3.2.1
- * Link: https://gitlab.com/samba-team/smb3-posix-spec/-/blob/master/fscc_posix_extensions.md
+ * See POSIX-FSCC 2.3.1
*/
typedef struct {
/* For undefined recommended transfer size return -1 in that field */
--
2.55.0
next prev parent reply other threads:[~2026-09-20 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 5:56 [PATCH 0/3] smb: update POSIX extension specification references ZhangGuoDong
2026-09-20 5:56 ` [PATCH 1/3] smb/server: " ZhangGuoDong
2026-09-20 14:03 ` Namjae Jeon
2026-09-21 0:35 ` ZhangGuoDong
2026-09-20 5:56 ` [PATCH 2/3] smb/client: " ZhangGuoDong
2026-09-20 5:56 ` ZhangGuoDong [this message]
2026-09-20 13:57 ` [PATCH 3/3] smb/common: " 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=20260920055653.114794-4-zhang.guodong@linux.dev \
--to=zhang.guodong@linux.dev \
--cc=chenxiaosong@kylinos.cn \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.org \
--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.