From: "Arnd Bergmann" <arnd@arndb.de>
To: linux-kernel@vger.kernel.org
Cc: "Marc Zyngier" <maz@kernel.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [irqchip: irq/irqchip-next] Revert "irqchip/mxs: Include linux/irqchip/mxs.h"
Date: Wed, 21 Jun 2023 15:37:55 +0200 [thread overview]
Message-ID: <246274e5-851d-4cea-8e01-d165ebd967f9@app.fastmail.com> (raw)
In-Reply-To: <168735222615.404.5437100914727545952.tip-bot2@tip-bot2>
On Wed, Jun 21, 2023, at 14:57, irqchip-bot for Marc Zyngier wrote:
> The following commit has been merged into the irq/irqchip-next branch
> of irqchip:
>
> Commit-ID: d93c22199966696cfb76c6942797de2fbb22da24
> Gitweb:
> https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms/d93c22199966696cfb76c6942797de2fbb22da24
> Author: Marc Zyngier <maz@kernel.org>
> AuthorDate: Wed, 21 Jun 2023 13:46:25 +01:00
> Committer: Marc Zyngier <maz@kernel.org>
> CommitterDate: Wed, 21 Jun 2023 13:50:53 +01:00
>
> Revert "irqchip/mxs: Include linux/irqchip/mxs.h"
>
> This reverts commit 5b7e5676209120814dbb9fec8bc3769f0f7a7958.
>
> Although including linux/irqchip/mxs.h is technically correct,
> this clashes with the parallel removal of this include file
> with 32bit ARM modernizing the low level irq handling as part of
> 5bb578a0c1b8 ("ARM: 9298/1: Drop custom mdesc->handle_irq()").
>
> As such, this patch is not only unnecessary, it also breaks
> compilation in -next. Revert it.
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Shawn Guo <shawnguo@kernel.org>
Thanks! I had prepared the same patch but not yet sent it as I
was still debugging some unrelated issues. Once 5bb578a0c1b8
ends up in mainline, we can get back to fixing the warning
by marking the handler as 'static'.
Arnd
prev parent reply other threads:[~2023-06-21 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 12:57 irqchip-bot for Marc Zyngier
2023-06-21 13:37 ` Arnd Bergmann [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=246274e5-851d-4cea-8e01-d165ebd967f9@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.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
all inboxes | Powered by JetHome®