From: Marc Zyngier <maz@kernel.org>
To: Ben Dooks <ben@fluff.org>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH] irqchip/mmp: fix missing extern init code
Date: Fri, 22 Jul 2022 09:09:49 +0100 [thread overview]
Message-ID: <87pmhxy3ea.wl-maz@kernel.org> (raw)
In-Reply-To: <20220722080333.4ic4n3bmsxs6kyyq@hetzy.fluff.org>
On Fri, 22 Jul 2022 09:03:33 +0100,
Ben Dooks <ben@fluff.org> wrote:
>
> On Fri, Jul 22, 2022 at 08:41:53AM +0100, Marc Zyngier wrote:
> > On Thu, 21 Jul 2022 22:51:47 +0100,
> > Ben Dooks <ben-linux@fluff.org> wrote:
> > >
> > > The functions icu_init_irq and mmp2_init_icu are exported
> > > from this code, so declare them in the header file to avoid
> > > the following sparse warnings:
>
> > $ git grep -E "icu_init_irq|mmp2_init_icu"
> > arch/arm/mach-mmp/mmp2.c: mmp2_init_icu();
> > arch/arm/mach-mmp/mmp2.h:extern void __init mmp2_init_icu(void);
> > arch/arm/mach-mmp/pxa168.c: icu_init_irq();
> > arch/arm/mach-mmp/pxa168.h:extern void __init icu_init_irq(void);
> > arch/arm/mach-mmp/pxa910.c: icu_init_irq();
> > arch/arm/mach-mmp/pxa910.h:extern void __init icu_init_irq(void);
> > drivers/irqchip/irq-mmp.c:void __init icu_init_irq(void)
> > drivers/irqchip/irq-mmp.c:void __init mmp2_init_icu(void)
> >
> > If you are going to fix this, please fix it sensibly.
>
> Ok, didn't realise these where not being built my the v7_multi defconfig.
> Should this all go into one patch or do the arch/arm bits need to go via
> some arm tree?
One single patch please, which I'll queue directly.
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2022-07-22 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 21:51 [PATCH] irqchip/mmp: fix missing extern init code Ben Dooks
2022-07-22 7:41 ` Marc Zyngier
2022-07-22 8:03 ` Ben Dooks
2022-07-22 8:09 ` 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=87pmhxy3ea.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=ben-linux@fluff.org \
--cc=ben@fluff.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.