From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jason Cooper <jason@lakedaemon.net>,
Magnus Damm <damm+renesas@opensource.se>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH 0/2] irqchip: make non-modular code explicitly non-modular
Date: Tue, 13 Oct 2015 22:26:14 -0400 [thread overview]
Message-ID: <20151014022613.GC25946@windriver.com> (raw)
In-Reply-To: <CAMuHMdUmerzvVGgspSoWZ+myspEcoZzRtdHjvK-EXZMp3kE=Ug@mail.gmail.com>
[Re: [PATCH 0/2] irqchip: make non-modular code explicitly non-modular] On 12/10/2015 (Mon 09:04) Geert Uytterhoeven wrote:
> Hi Paul,
>
> On Mon, Oct 12, 2015 at 1:05 AM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
[...]
> > Paul Gortmaker (2):
> > drivers/irqchip: make irq-renesas-intc-irqpin.c explicitly non-modular
> > drivers/irqchip: make irq-renesas-irqc.c explicitly non-modular
> >
> > drivers/irqchip/irq-renesas-intc-irqpin.c | 24 +-----------------------
> > drivers/irqchip/irq-renesas-irqc.c | 30 +-----------------------------
> > 2 files changed, 2 insertions(+), 52 deletions(-)
>
> Both of these are "external interrupt controllers", meaning that on some boards
> they are used to handle only interrupts from external devices (e.g. Ethernet),
> which is optional.
>
> Hence IMHO the bool should be changed to tristate instead.
So, at the risk of repeating myself -- changing to tristate widens the
scope on build coverage and everything else. When I did this for a
staging driver, I got caught in symbols that were not exported. Not
critically complex, but it does show that allowing a new config option
can make things break. Hence keeping the support matrix the same is
table stakes to allow me to make this tree wide update in a way that
scales.
As the changes I propose do not change the runtime, I think that the
verification of the extension of functionality lies on those who think
moving these drivers from bool to tristate is a genuine value add.
If for no other reason, it at least does keep a bisect honest in showing
where existing functionality broke vs. added functionality brought in
new breakage.
Paul.
--
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
prev parent reply other threads:[~2015-10-14 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 23:05 [PATCH 0/2] irqchip: make non-modular code explicitly non-modular Paul Gortmaker
2015-10-11 23:05 ` [PATCH 1/2] drivers/irqchip: make irq-renesas-intc-irqpin.c " Paul Gortmaker
2015-10-11 23:05 ` [PATCH 2/2] drivers/irqchip: make irq-renesas-irqc.c " Paul Gortmaker
2015-10-12 7:04 ` [PATCH 0/2] irqchip: make non-modular code " Geert Uytterhoeven
2015-10-14 2:26 ` Paul Gortmaker [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=20151014022613.GC25946@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=damm+renesas@opensource.se \
--cc=geert@linux-m68k.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--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