From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
David Laight <david.laight.linux@gmail.com>,
Kees Cook <kees@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Nathan Chancellor <nathan@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v9 0/6] lib and lib/cmdline enhancements
Date: Fri, 3 Apr 2026 10:09:46 -0700 [thread overview]
Message-ID: <20260403100946.de777cb981de664f28089d99@linux-foundation.org> (raw)
In-Reply-To: <20260403103338.1122415-1-dmantipov@yandex.ru>
On Fri, 3 Apr 2026 13:33:32 +0300 Dmitry Antipov <dmantipov@yandex.ru> wrote:
> Adjust '_parse_integer_limit()' and 'memparse()' to not ignore overflows,
> extend string to 64-bit integer conversion tests, add KUnit-based test
> for 'memparse()', fix kernel-doc glitches found in lib/cmdline.c and
> adjust riscv32 linker script to export symbols needed for EFI stub.
Thanks, Dmitry.
I've updated mm.git's mm-nonmm-unstable with this version. I'll aim to
upstream this series during the upcoming merge window.
Here's how the v9 series altered mm.git:
arch/riscv/kernel/image-vars.h | 9 +++++++++
1 file changed, 9 insertions(+)
--- a/arch/riscv/kernel/image-vars.h~b
+++ a/arch/riscv/kernel/image-vars.h
@@ -32,6 +32,15 @@ __efistub___init_text_end = __init_text_
__efistub_sysfb_primary_display = sysfb_primary_display;
#endif
+#ifdef CONFIG_CC_IS_GCC
+/*
+ * Double-word integer shifts are used by the library code and so EFI stub as
+ * well. Not needed for clang and please let me know if anyone understands why.
+ */
+PROVIDE(__efistub___lshrdi3 = __lshrdi3);
+PROVIDE(__efistub___ashldi3 = __ashldi3);
+#endif /* CONFIG_CC_IS_GCC */
+
#endif
#endif /* __RISCV_KERNEL_IMAGE_VARS_H */
_
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-04-03 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 10:33 [PATCH v9 0/6] lib and lib/cmdline enhancements Dmitry Antipov
2026-04-03 10:33 ` [PATCH v9 1/6] lib: fix _parse_integer_limit() to handle overflow Dmitry Antipov
2026-04-03 10:33 ` [PATCH v9 2/6] lib: fix memparse() " Dmitry Antipov
2026-04-03 10:33 ` [PATCH v9 3/6] lib: add more string to 64-bit integer conversion overflow tests Dmitry Antipov
2026-04-03 10:33 ` [PATCH v9 4/6] lib/cmdline_kunit: add test case for memparse() Dmitry Antipov
2026-04-03 10:33 ` [PATCH v9 5/6] lib/cmdline: adjust a few comments to fix kernel-doc -Wreturn warnings Dmitry Antipov
2026-04-03 10:33 ` [PATCH v9 6/6] riscv: export symbols needed for riscv32 EFI stub Dmitry Antipov
2026-04-09 5:00 ` Charlie Jenkins
2026-04-09 8:51 ` Andy Shevchenko
2026-04-03 17:09 ` Andrew Morton [this message]
2026-04-03 19:25 ` [PATCH v9 0/6] lib and lib/cmdline enhancements Andrew Morton
2026-04-05 9:13 ` Dmitry Antipov
2026-04-07 16:12 ` Andy Shevchenko
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=20260403100946.de777cb981de664f28089d99@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=djwong@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=kees@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nathan@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
/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