From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: ye.xingchen@zte.com.cn, brauner@kernel.org
Cc: jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nls: Fix utf32_to_utf8 parameter type in declaration and definition
Date: Thu, 13 Mar 2025 08:52:52 -0700 [thread overview]
Message-ID: <1e8a650d-dd87-4ff3-ad83-da9e7f33a915@oss.qualcomm.com> (raw)
In-Reply-To: <202503131601265834sSbkAuqH0NUydxGXf-Fa@zte.com.cn>
On 3/13/2025 1:01 AM, ye.xingchen@zte.com.cn wrote:
> From: YeXingchen <ye.xingchen@zte.com.cn>
>
> The declaration of utf32_to_utf8 in the header file uses
> bool maxlen as the parameter type, while the definition uses bool maxout.
>
> This patch aligns the parameter name in the definition with the
> declaration,changing maxout to maxlen to ensure consistency.
>
> Signed-off-by: YeXingchen <ye.xingchen@zte.com.cn>
> ---
> fs/nls/nls_base.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/nls/nls_base.c b/fs/nls/nls_base.c
> index 18d597e49a19..1dc2f8c8916e 100644
> --- a/fs/nls/nls_base.c
> +++ b/fs/nls/nls_base.c
> @@ -83,7 +83,7 @@ int utf8_to_utf32(const u8 *s, int inlen, unicode_t *pu)
> }
> EXPORT_SYMBOL(utf8_to_utf32);
>
> -int utf32_to_utf8(unicode_t u, u8 *s, int maxout)
> +int utf32_to_utf8(unicode_t u, u8 *s, int maxlen)
> {
> unsigned long l;
> int c, nc;
It is obvious you didn't compile this code since the implementation still uses
maxout. Note that a less intrusive change would be to rename parameters in the
prototype.
prev parent reply other threads:[~2025-03-13 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 8:01 [PATCH] nls: Fix utf32_to_utf8 parameter type in declaration and definition ye.xingchen
2025-03-13 15:52 ` Jeff Johnson [this message]
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=1e8a650d-dd87-4ff3-ad83-da9e7f33a915@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ye.xingchen@zte.com.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox