From: Nathan Chancellor <nathan@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [linux-next:master 10394/11136] arch/riscv/Kconfig:67: syntax error
Date: Fri, 19 Sep 2025 13:50:01 -0700 [thread overview]
Message-ID: <20250919205001.GA3249395@ax162> (raw)
In-Reply-To: <202509200414.Q0j4r2Pc-lkp@intel.com>
On Sat, Sep 20, 2025 at 04:29:50AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 846bd2225ec3cfa8be046655e02b9457ed41973e
> commit: df4c83704cac9531e91cd161dd8a2b0857b8bb2d [10394/11136] Merge 6.17-rc6 into kbuild-next
> config: riscv-randconfig-002-20250920 (attached as .config)
> compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 7c861bcedf61607b6c087380ac711eb7ff918ca6)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250920/202509200414.Q0j4r2Pc-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/202509200414.Q0j4r2Pc-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> arch/riscv/Kconfig:67: syntax error
> arch/riscv/Kconfig:67: invalid statement
That's embarrassing :/
Fixed in kbuild-next now, thanks for the report!
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git/commit/arch/riscv/Kconfig?id=95ee3364b29313a7587b7d1e42a9d043aaf7e592
Cheers,
Nathan
prev parent reply other threads:[~2025-09-19 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 20:29 [linux-next:master 10394/11136] arch/riscv/Kconfig:67: syntax error kernel test robot
2025-09-19 20:50 ` Nathan Chancellor [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=20250919205001.GA3249395@ax162 \
--to=nathan@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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