All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: arch/x86/Kconfig:2368: syntax error
Date: Wed, 30 Sep 2026 11:18:47 +0100	[thread overview]
Message-ID: <arzh5K2jsUmN1pWt@gremlin> (raw)
In-Reply-To: <202609291906.GAlpG7h2-lkp@intel.com>

On Tue, Sep 29, 2026 at 07:34:56PM +0200, kernel test robot wrote:
> tree:   https://github.com/intel-lab-lkp/linux/commits/Lorenzo-Stoakes-ARM/kbuild-do-not-allocate-modinfo-in-vmlinux/20260923-181750
> head:   7037b569f2880edc0732da253bce262da253ac12
> commit: 7a5e3a047b46532027b586ea704af1fc8677ef19 kbuild: avoid re-running compiler and linker probes
> date:   6 days ago
> config: x86_64-rhel-9.4-ltp (attached as .config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260929/202609291906.GAlpG7h2-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/202609291906.GAlpG7h2-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>    scripts/Kconfig.toolchain:148: syntax error
>    scripts/Kconfig.toolchain:148: unknown statement "def_string"

Similar to the other robot report, this is just the dependencies not being
applied (as stated in cover letter).

--
Cheers, Lorenzo

      reply	other threads:[~2026-09-30 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 17:34 arch/x86/Kconfig:2368: syntax error kernel test robot
2026-09-30 10:18 ` Lorenzo Stoakes (ARM) [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=arzh5K2jsUmN1pWt@gremlin \
    --to=ljs@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.