public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Kees Cook <kees@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
	llvm@lists.linux.dev, linux-efi@vger.kernel.org
Subject: Re: [PATCH RFC 2/2] wcslen() prototype in string.h
Date: Tue, 25 Mar 2025 18:17:34 +0200	[thread overview]
Message-ID: <Z-LXHssrcpdtFqqn@smile.fi.intel.com> (raw)
In-Reply-To: <20250325-string-add-wcslen-for-llvm-opt-v1-2-b8f1e2c17888@kernel.org>

On Tue, Mar 25, 2025 at 08:45:19AM -0700, Nathan Chancellor wrote:
> If this is desired, it should be squashed into the previous change. I
> wrote it separately because it is slightly more invasive.
> 
> In order to export wcslen() to the rest of the kernel (should it ever be
> necessary elsewhere), it needs to be added to string.h, along with nls.h
> for the typedef of wchar_t. However, dragging in nls.h into string.h
> causes an error in the efistub due to a conflicting function name:
> 
>   drivers/firmware/efi/libstub/printk.c:27:5: error: static declaration of 'utf8_to_utf32' follows non-static declaration
>      27 | u32 utf8_to_utf32(const u8 **s8)
>         |     ^
>   include/linux/nls.h:55:12: note: previous declaration is here
>      55 | extern int utf8_to_utf32(const u8 *s, int len, unicode_t *pu);
>         |            ^
>   drivers/firmware/efi/libstub/printk.c:85:26: error: too few arguments to function call, expected 3, have 1
>      85 |                 c32 = utf8_to_utf32(&s8);
>         |                       ~~~~~~~~~~~~~    ^
>   include/linux/nls.h:55:12: note: 'utf8_to_utf32' declared here
>      55 | extern int utf8_to_utf32(const u8 *s, int len, unicode_t *pu);
>         |            ^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2 errors generated.
> 
> Rename the efi function to avoid the conflict.

Hmm... Why not split this to two, rename patch as a standalone makes sense to
me even outside of this series.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-03-25 16:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 15:45 [PATCH 0/2] string.c: Add wcslen() Nathan Chancellor
2025-03-25 15:45 ` [PATCH 1/2] lib/string.c: " Nathan Chancellor
2025-03-25 15:45 ` [PATCH RFC 2/2] wcslen() prototype in string.h Nathan Chancellor
2025-03-25 16:17   ` Andy Shevchenko [this message]
2025-03-25 16:58     ` Nathan Chancellor
2025-03-25 17:05       ` Andy Shevchenko
2025-03-25 21:45         ` Nathan Chancellor
2025-03-26  0:33           ` Nathan Chancellor
2025-03-26  8:59             ` Andy Shevchenko
2025-03-26 15:37               ` Nathan Chancellor
2025-03-26 15:43                 ` Andy Shevchenko
2025-03-26  8:52           ` Andy Shevchenko
2025-03-25 23:55   ` kernel test robot

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=Z-LXHssrcpdtFqqn@smile.fi.intel.com \
    --to=andy@kernel.org \
    --cc=ardb@kernel.org \
    --cc=justinstitt@google.com \
    --cc=kees@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.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