[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <103ac0c4-486c-44c0-926c-8cc5b1387efa@web.de>
Date: Sat, 18 Oct 2025 20:30:18 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: chenxiaosong@...inos.cn, linux-cifs@...r.kernel.org,
Namjae Jeon <linkinjeon@...nel.org>, Namjae Jeon <linkinjeon@...ba.org>,
Steve French <sfrench@...ba.org>, Steve French <smfrench@...il.com>
Cc: chenxiaosong.chenxiaosong@...ux.dev, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/6] smb/server: fix return value of smb2_notify()
> smb2_notify() should return error code when an error occurs,
> __process_request() will print the error messages.
>
> I may implement the SMB2 CHANGE_NOTIFY response (see MS-SMB2 2.2.36)
> in the future.
Will another imperative wording approach become more helpful for an improved
change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc1#n94
Regards,
Markus
Powered by blists - more mailing lists