[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86a66m8lml.wl-maz@kernel.org>
Date: Mon, 26 Sep 2022 06:40:02 -0400
From: Marc Zyngier <maz@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 5.4 097/120] gpio: ixp4xx: Make irqchip immutable
Greg,
On Mon, 26 Sep 2022 06:12:10 -0400,
Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
>
> From: Linus Walleij <linus.walleij@...aro.org>
>
> [ Upstream commit 94e9bc73d85aa6ecfe249e985ff57abe0ab35f34 ]
>
> This turns the IXP4xx GPIO irqchip into an immutable
> irqchip, a bit different from the standard template due
> to being hierarchical.
>
> Tested on the IXP4xx which uses drivers/ata/pata_ixp4xx_cf.c
> for a rootfs on compact flash with IRQs from this GPIO
> block to the CF ATA controller.
>
> Cc: Marc Zyngier <maz@...nel.org>
> Signed-off-by: Linus Walleij <linus.walleij@...aro.org>
> Acked-by: Marc Zyngier <maz@...nel.org>
> Signed-off-by: Bartosz Golaszewski <brgl@...ev.pl>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
We had that discussion[1], and concluded that none of these should be
backported to a kernel earlier than 5.19. 5.4 doesn't currently
contain the relevant infrastructure, nor should that infrastructure
should be backported either.
Can we *please* stop this?
M.
[1] https://lore.kernel.org/all/CAMRc=Md9JKdW8wmbun_0_1y2RQbck7q=vzOkdw6n+FBgpf0h8w@mail.gmail.com/
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists