From: ChenXiaoSong <chenxiaosong.chenxiaosong@linux.dev>
To: David Howells <dhowells@redhat.com>, chenxiaosong.chenxiaosong@linux.dev
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,
linux-cifs@vger.kernel.org, Steve French <stfrench@microsoft.com>
Subject: Re: [PATCH v7 2/5] cifs: Autogenerate SMB2 error mapping table
Date: Mon, 5 Jan 2026 16:03:13 +0800 [thread overview]
Message-ID: <5677f64a-9607-41b9-93d4-7c256d1bbb14@linux.dev> (raw)
In-Reply-To: <1696856.1767599900@warthog.procyon.org.uk>
The SMB code currently uses __u32, __u16, __u8. Perhaps we can consider
replacing them all with u32, u16, u8 in the future.
Thanks,
ChenXiaoSong <chenxiaosong@kylinos.cn>
On 1/5/26 15:58, David Howells wrote:
> Note that you only really need to use __u32, __u16, __u8 and suchlike in UAPI
> structs that userspace will be able to #include. You can use u32, u16, u8 in
> kernel internals. But don't worry too much about it - it's not worth
> respinning the patches over.
next prev parent reply other threads:[~2026-01-05 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 13:09 [PATCH v7 0/5] smb: improve search speed of SMB2 maperror chenxiaosong.chenxiaosong
2025-12-31 13:09 ` [PATCH v7 1/5] cifs: Label SMB2 statuses with errors chenxiaosong.chenxiaosong
2025-12-31 13:09 ` [PATCH v7 2/5] cifs: Autogenerate SMB2 error mapping table chenxiaosong.chenxiaosong
2026-01-05 7:58 ` David Howells
2026-01-05 8:03 ` ChenXiaoSong [this message]
2026-01-05 8:15 ` David Howells
2025-12-31 13:09 ` [PATCH v7 3/5] smb/client: check whether smb2_error_map_table is sorted in ascending order chenxiaosong.chenxiaosong
2025-12-31 13:09 ` [PATCH v7 4/5] smb/client: use bsearch() to find target in smb2_error_map_table chenxiaosong.chenxiaosong
2026-01-05 8:02 ` David Howells
2025-12-31 13:09 ` [PATCH v7 5/5] smb/client: introduce KUnit test to check search result of smb2_error_map_table chenxiaosong.chenxiaosong
2026-01-05 8:04 ` David Howells
2026-01-05 8:09 ` 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=5677f64a-9607-41b9-93d4-7c256d1bbb14@linux.dev \
--to=chenxiaosong.chenxiaosong@linux.dev \
--cc=bharathsm@microsoft.com \
--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