From: "Björn Töpel" <bjorn@kernel.org>
To: kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
amd-gfx@lists.freedesktop.org, bpf@vger.kernel.org,
dmaengine@vger.kernel.org, dri-devel@lists.freedesktop.org,
imx@lists.linux.dev, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, linux-arch@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-pm@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
linux-riscv@lists.infradead.org, netdev@vger.kernel.org,
nouveau@lists.freedesktop.org
Subject: Re: [linux-next:master] BUILD REGRESSION 124cfbcd6d185d4f50be02d5f5afe61578916773
Date: Tue, 21 May 2024 18:43:38 +0200 [thread overview]
Message-ID: <87wmnncdz9.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <202405220033.NXFpd4Af-lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 124cfbcd6d185d4f50be02d5f5afe61578916773 Add linux-next specific files for 20240521
[...]
> Error/Warning ids grouped by kconfigs:
>
> gcc_recent_errors
[...]
> |-- riscv-randconfig-r054-20240521
> | `--
> drivers-irqchip-irq-riscv-imsic-early.c:error:too-many-arguments-to-function-riscv_ipi_set_virq_range
FWIW, discussion/patch here [1]
Björn
[1] https://lore.kernel.org/linux-riscv/mhng-10b71228-cf3e-42ca-9abf-5464b15093f1@palmer-ri-x1c9/
prev parent reply other threads:[~2024-05-21 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 16:27 [linux-next:master] BUILD REGRESSION 124cfbcd6d185d4f50be02d5f5afe61578916773 kernel test robot
2024-05-21 16:43 ` Björn Töpel [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=87wmnncdz9.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bpf@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nouveau@lists.freedesktop.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).