From: Tony Prisk <linux@prisktech.co.nz>
To: Axel Lin <axel.lin@ingics.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Olof Johansson <olof@lixom.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip: vt8500: Staticize local symbols
Date: Fri, 05 Jul 2013 06:32:41 +1200 [thread overview]
Message-ID: <51D5BFC9.6090703@prisktech.co.nz> (raw)
In-Reply-To: <1372918293.25529.2.camel@phoenix>
On 04/07/13 18:11, Axel Lin wrote:
> This driver is converted to use IRQCHIP_DECLARE and irqchip_init.
> vt8500_handle_irq() and vt8500_irq_init() are only referenced in this file now,
> make them static.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> drivers/irqchip/irq-vt8500.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/irqchip/irq-vt8500.c b/drivers/irqchip/irq-vt8500.c
> index d970595..1846e7d 100644
> --- a/drivers/irqchip/irq-vt8500.c
> +++ b/drivers/irqchip/irq-vt8500.c
> @@ -178,7 +178,8 @@ static struct irq_domain_ops vt8500_irq_domain_ops = {
> .xlate = irq_domain_xlate_onecell,
> };
>
> -asmlinkage void __exception_irq_entry vt8500_handle_irq(struct pt_regs *regs)
> +static asmlinkage
> +void __exception_irq_entry vt8500_handle_irq(struct pt_regs *regs)
> {
> u32 stat, i;
> int irqnr, virq;
> @@ -203,7 +204,8 @@ asmlinkage void __exception_irq_entry vt8500_handle_irq(struct pt_regs *regs)
> }
> }
>
> -int __init vt8500_irq_init(struct device_node *node, struct device_node *parent)
> +static int __init vt8500_irq_init(struct device_node *node,
> + struct device_node *parent)
I prefer that the function variables are lined up, rather than aligning
with the (. Can you move the 'struct device_node *parent' across one
more space?
Otherwise:
Acked-by: Tony Prisk <linux@prisktech.co.nz>
> {
> int irq, i;
> struct device_node *np = node;
Regards
Tony P
prev parent reply other threads:[~2013-07-04 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 6:11 [PATCH] irqchip: vt8500: Staticize local symbols Axel Lin
2013-07-04 18:32 ` Tony Prisk [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=51D5BFC9.6090703@prisktech.co.nz \
--to=linux@prisktech.co.nz \
--cc=axel.lin@ingics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--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