[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-af1916da-8846-4b63-a3c9-4bc3a50c0646@palmer-ri-x1c9a>
Date: Mon, 17 Jul 2023 15:18:37 -0700 (PDT)
From: Palmer Dabbelt <palmer@...belt.com>
To: samuel.holland@...ive.com
CC: linus.walleij@...aro.org, brgl@...ev.pl, andy@...nel.org,
robh+dt@...nel.org, frowand.list@...il.com,
samuel.holland@...ive.com,
Paul Walmsley <paul.walmsley@...ive.com>,
devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH 0/2] gpio: sifive: Module support
On Mon, 17 Jul 2023 13:53:55 PDT (-0700), samuel.holland@...ive.com wrote:
> With of_irq_count() exported, the SiFive GPIO driver can be built as a
> module. This helps to minimize the size of a multiplatform kernel, and
> is required by some downstream distributions (Android GKI).
>
>
> Samuel Holland (2):
> of/irq: Export of_irq_count()
> gpio: sifive: Allow building the driver as a module
>
> drivers/gpio/Kconfig | 2 +-
> drivers/gpio/gpio-sifive.c | 4 +++-
> drivers/of/irq.c | 1 +
> 3 files changed, 5 insertions(+), 2 deletions(-)
Acked-by: Palmer Dabbelt <palmer@...osinc.com>
I guess we probably should have just done that the first time around?
Either way it seems reasonable to me, aside from sorting out the OF
stuff.
Powered by blists - more mailing lists