linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 02/11] irqchip: mmp: support irqchip
Date: Mon, 3 Jun 2013 18:06:05 +0800	[thread overview]
Message-ID: <CAN1soZxWDGit540wZvxUDMDCUO_BTZnBLXrMKU4NAYeaEfe7BA@mail.gmail.com> (raw)
In-Reply-To: <20130603094200.GH18614@n2100.arm.linux.org.uk>

On Mon, Jun 3, 2013 at 5:42 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Jun 03, 2013 at 05:30:36PM +0800, Haojian Zhuang wrote:
>> @@ -64,7 +60,7 @@ static const char *mmp_dt_board_compat[] __initdata = {
>>
>>  DT_MACHINE_START(PXA168_DT, "Marvell PXA168 (Device Tree Support)")
>>       .map_io         = mmp_map_io,
>> -     .init_irq       = mmp_dt_irq_init,
>> +     .init_irq       = irqchip_init,
>>       .init_time      = mmp_dt_init_timer,
>>       .init_machine   = pxa168_dt_init,
>>       .dt_compat      = mmp_dt_board_compat,
>> @@ -72,7 +68,7 @@ MACHINE_END
>>
>>  DT_MACHINE_START(PXA910_DT, "Marvell PXA910 (Device Tree Support)")
>>       .map_io         = mmp_map_io,
>> -     .init_irq       = mmp_dt_irq_init,
>> +     .init_irq       = irqchip_init,
>
> This is what's in linux-next:
>
> void __init init_IRQ(void)
> {
>         if (IS_ENABLED(CONFIG_OF) && !machine_desc->init_irq)
>                 irqchip_init();
>         else
>                 machine_desc->init_irq();
> }
>
> So just set your .init_irq to NULL after basing your patchset on
> ebafed7ab9b637656b685f1dc1ee528c77241a0d (ARM: irq: Call irqchip_init
> if no init_irq function is specified).

OK. I'll update it.

Regards
Haojian

  reply	other threads:[~2013-06-03 10:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  9:30 [PATCH v3 00/11] update irqchip, clocksource, clk in mmp Haojian Zhuang
2013-06-03  9:30 ` [PATCH v3 01/11] irqchip: move mmp irq driver Haojian Zhuang
2013-06-03  9:30 ` [PATCH v3 02/11] irqchip: mmp: support irqchip Haojian Zhuang
2013-06-03  9:42   ` Russell King - ARM Linux
2013-06-03 10:06     ` Haojian Zhuang [this message]
2013-06-03  9:30 ` [PATCH v3 03/11] irqchip: mmp: support MULTI_IRQ_HANDLER Haojian Zhuang
2013-06-03  9:30 ` [PATCH v3 04/11] ARM: mmp: avoid to include head file in mach-mmp Haojian Zhuang
2013-06-03 22:28   ` Arnd Bergmann
2013-06-03  9:30 ` [PATCH v3 05/11] irqchip: mmp: avoid to include irqs head file Haojian Zhuang
2013-06-03  9:30 ` [PATCH v3 06/11] clocksource: mmp: move mmp timer driver Haojian Zhuang
2013-06-03  9:30 ` [PATCH v3 07/11] ARM: mmp: move timer registers into driver Haojian Zhuang
2013-06-03 22:31   ` Arnd Bergmann
2013-06-03  9:30 ` [PATCH v3 08/11] ARM: pxa: init dma debugfs in late level Haojian Zhuang
2013-06-03  9:30 ` [PATCH v3 09/11] clk: mmp: parse clock from dts Haojian Zhuang
2013-06-03  9:30 ` [PATCH v3 10/11] ARM: mmp: avoid to use cpu_is_xxx in timer Haojian Zhuang
2013-06-03 22:34   ` Arnd Bergmann
2013-06-04  1:24     ` Haojian Zhuang
2013-06-03  9:30 ` [PATCH v3 11/11] ARCH: mmp: support clocksource " Haojian Zhuang
2013-06-03 17:07   ` John Stultz
2013-06-04  1:25     ` Haojian Zhuang

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=CAN1soZxWDGit540wZvxUDMDCUO_BTZnBLXrMKU4NAYeaEfe7BA@mail.gmail.com \
    --to=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).