From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: "Aurélien Aptel" <aurelien.aptel@gmail.com>
Cc: smfrench@gmail.com, linkinjeon@kernel.org, pc@manguebit.org,
ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
bharathsm@microsoft.com, senozhatsky@chromium.org,
dhowells@redhat.com, linux-cifs@vger.kernel.org,
Steve French <stfrench@microsoft.com>,
ChenXiaoSong <chenxiaosong@kylinos.cn>
Subject: Re: [PATCH v8 2/5] cifs: Autogenerate SMB2 error mapping table
Date: Fri, 16 Jan 2026 22:51:28 +0800 [thread overview]
Message-ID: <38a0be75-0884-4808-a840-fc9e8f2ee6a0@linux.dev> (raw)
In-Reply-To: <CA+5B0FOT_H1vO+9cfSbpFsUauQ_V1KM0GGKjp=+_K+z-SEWNeA@mail.gmail.com>
In the future, when adding new elements to SMB2_ERR_LIST, we would need
a script to reorder them, which seems difficult to maintain.
Thanks,
ChenXiaoSong <chenxiaosong@kylinos.cn>
On 1/16/26 21:48, Aurélien Aptel wrote:
> #define SMB2_ERR_LIST \
> X(STATUS_WAIT_1, 0x00000000, -EIO, <whatever else>) \
> X(STATUS_WAIT_2, 0x00000001, -EIO, <whatever else>) \
> ...
next prev parent reply other threads:[~2026-01-16 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 7:15 [PATCH v8 0/5] smb: improve search speed of SMB2 maperror chenxiaosong.chenxiaosong
2026-01-06 7:15 ` [PATCH v8 1/5] cifs: Label SMB2 statuses with errors chenxiaosong.chenxiaosong
2026-01-06 7:15 ` [PATCH v8 2/5] cifs: Autogenerate SMB2 error mapping table chenxiaosong.chenxiaosong
2026-01-16 8:14 ` ChenXiaoSong
2026-01-16 13:48 ` Aurélien Aptel
2026-01-16 14:30 ` ChenXiaoSong
2026-01-16 14:51 ` ChenXiaoSong [this message]
2026-01-06 7:15 ` [PATCH v8 3/5] smb/client: check whether smb2_error_map_table is sorted in ascending order chenxiaosong.chenxiaosong
2026-01-06 7:15 ` [PATCH v8 4/5] smb/client: use bsearch() to find target in smb2_error_map_table chenxiaosong.chenxiaosong
2026-01-06 7:15 ` [PATCH v8 5/5] smb/client: introduce KUnit test to check search result of smb2_error_map_table chenxiaosong.chenxiaosong
2026-01-06 9:34 ` [PATCH v8 0/5] smb: improve search speed of SMB2 maperror David Howells
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=38a0be75-0884-4808-a840-fc9e8f2ee6a0@linux.dev \
--to=chenxiaosong.chenxiaosong@linux.dev \
--cc=aurelien.aptel@gmail.com \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@kylinos.cn \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=stfrench@microsoft.com \
--cc=tom@talpey.com \
/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