From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
David Laight <david.laight.linux@gmail.com>,
Kees Cook <kees@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/5] lib and lib/cmdline enhancements
Date: Thu, 2 Apr 2026 19:09:21 +0300 [thread overview]
Message-ID: <ac6UsaCCJQjFtpLA@ashevche-desk.local> (raw)
In-Reply-To: <20260402090030.b5a03939994b3b426ea37032@linux-foundation.org>
On Thu, Apr 02, 2026 at 09:00:30AM -0700, Andrew Morton wrote:
> On Thu, 2 Apr 2026 11:30:43 +0300 Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> > > > > > lib/cmdline_kunit: add test case for memparse()
> > > > > > lib/cmdline: adjust a few comments to fix kernel-doc -Wreturn warnings
> > > > >
> > > > > Any chance to move forward with this?
> > > >
> > > > I think it's a grace period due to ongoing merge window.
> > > > Also we need more input on the first patch from others,
> > > > perhaps Kees and Andrew can take a look when they will be
> > > > less busy.
> > >
> > > The same question again...
> >
> > I'm not sure why. The patches are in Linux Next for several days already.
> > $ git tag --contains b85c7e022e1c # the last one
> > next-20260401
> >
> > Yet it needs to be merged into nomm-stable (if I understood the process right).
>
> Yes, these are on track for the upcoming merge window.
>
> However I believe the riscv32 build breakage remains unresolved?
>
> https://lore.kernel.org/all/202603041925.KLKqpK6N-lkp@intel.com/T/#u
I haven't heard any move of that. Ard proposed a fix/workaround. Nobody seems care.
So I think leaving it as is is also okay as risc-v people simply do not care.
Alternatively we may apply one of the suggested approaches: disabling EFI for 32-bit
or a patch that enables shift from a GCC library — in-kernel copy of it.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-04-02 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 16:44 [PATCH v8 0/5] lib and lib/cmdline enhancements Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 1/5] lib: fix _parse_integer_limit() to handle overflow Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 2/5] lib: fix memparse() " Dmitry Antipov
2026-02-24 12:32 ` Rodrigo Alencar
2026-02-24 14:15 ` Rodrigo Alencar
2026-02-25 6:58 ` Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 3/5] lib: add more string to 64-bit integer conversion overflow tests Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 4/5] lib/cmdline_kunit: add test case for memparse() Dmitry Antipov
2026-02-12 16:44 ` [PATCH v8 5/5] lib/cmdline: adjust a few comments to fix kernel-doc -Wreturn warnings Dmitry Antipov
2026-02-18 13:40 ` [PATCH v8 0/5] lib and lib/cmdline enhancements Dmitry Antipov
2026-02-18 13:48 ` Andy Shevchenko
2026-04-02 6:56 ` Dmitry Antipov
2026-04-02 8:30 ` Andy Shevchenko
2026-04-02 16:00 ` Andrew Morton
2026-04-02 16:09 ` Andy Shevchenko [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=ac6UsaCCJQjFtpLA@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david.laight.linux@gmail.com \
--cc=djwong@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.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