Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>,
	Dmitry Antipov <dmantipov@yandex.ru>,
	oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 14086/14440] lib/cmdline.c:188: undefined reference to `__efistub___lshrdi3'
Date: Wed, 13 May 2026 13:30:07 +0300	[thread overview]
Message-ID: <agRSr3EqFmPkBZ1e@ashevche-desk.local> (raw)
In-Reply-To: <20260512205908.7817ac71eb93427b17518ca7@linux-foundation.org>

On Tue, May 12, 2026 at 08:59:08PM -0700, Andrew Morton wrote:
> On Mon, 04 May 2026 13:22:00 +0800 kernel test robot <lkp@intel.com> wrote:
> 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head:   b9303e6bff706758c167af686b5315ad00233bf8
> > commit: 7f448f913d6f048e448df40a877be6f5afb5249d [14086/14440] lib: fix memparse() to handle overflow
> > config: riscv-randconfig-001-20260504 (https://download.01.org/0day-ci/archive/20260504/202605041353.nsZSMiIC-lkp@intel.com/config)
> > compiler: riscv32-linux-gcc (GCC) 8.5.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260504/202605041353.nsZSMiIC-lkp@intel.com/reproduce)
> > 
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202605041353.nsZSMiIC-lkp@intel.com/
> > 
> > All errors (new ones prefixed by >>):
> > 
> >    riscv32-linux-ld: ./drivers/firmware/efi/libstub/lib-cmdline.stub.o: in function `memparse':
> > >> lib/cmdline.c:188: undefined reference to `__efistub___lshrdi3'
> 
> Still there.  
> 
> Thanks.  I've forgotten what's happening here, and I'm probably not the
> only one!  I'll remove the "lib and lib/cmdline enhancements, v9"
> series from mm.git - Dmitry, please let's start again?

Yes, please. The consensus (almost?) was to get a v10 that incorporates /
combines the two:
- the v7 for risc-v fixes (available in ML)
- the v9 rebased on top of the above

-- 
With Best Regards,
Andy Shevchenko




      reply	other threads:[~2026-05-13 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04  5:22 [linux-next:master 14086/14440] lib/cmdline.c:188: undefined reference to `__efistub___lshrdi3' kernel test robot
2026-05-13  3:59 ` Andrew Morton
2026-05-13 10:30   ` 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=agRSr3EqFmPkBZ1e@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmantipov@yandex.ru \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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