From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
lkft-triage@lists.linaro.org, Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: next: drivers/irqchip/irq-mxs.c:12:10: fatal error: linux/irqchip/mxs.h: No such file or directory
Date: Wed, 21 Jun 2023 13:52:32 +0100 [thread overview]
Message-ID: <87v8fhou3z.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+G9fYtoB7nxiNp23PyHwZpODwA0OPFfbUaK_PWiV9DO34VKjA@mail.gmail.com>
On Wed, 21 Jun 2023 12:28:34 +0100,
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Following build regressions noticed on Linux next-20230620 and next-20230621.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Regressions found on arm:
>
> - build/gcc-12-mxs_defconfig
> - build/clang-nightly-mxs_defconfig
> - build/gcc-8-mxs_defconfig
> - build/clang-16-mxs_defconfig
>
> Build log:
> --------
> drivers/irqchip/irq-mxs.c:12:10: fatal error: linux/irqchip/mxs.h: No
> such file or directory
> 12 | #include <linux/irqchip/mxs.h>
> | ^~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
This include file is getting removed in parallel... I'll revert the
patch in my tree.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-06-21 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 11:28 next: drivers/irqchip/irq-mxs.c:12:10: fatal error: linux/irqchip/mxs.h: No such file or directory Naresh Kamboju
2023-06-21 12:52 ` Marc Zyngier [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=87v8fhou3z.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/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 NNTP newsgroup(s).