From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 09/14] ARM: mvebu: Remove init_irq declaration in machine description
Date: Mon, 13 May 2013 17:53:37 +0200 [thread overview]
Message-ID: <51910C81.5050501@free-electrons.com> (raw)
In-Reply-To: <20130513151934.GM31290@titan.lakedaemon.net>
Hi Jason,
Le 13/05/2013 17:19, Jason Cooper a ?crit :
> On Mon, May 13, 2013 at 11:44:08AM +0200, Maxime Ripard wrote:
>> Commit ebafed7a ("ARM: irq: Call irqchip_init if no init_irq function is
>> specified") removed the need to explictly setup the init_irq field in
>> the machine description when using only irqchip_init. Remove that
>> declaration for mvebu as well.
>>
>> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>> ---
>> arch/arm/mach-mvebu/armada-370-xp.c | 1 -
>> 1 file changed, 1 deletion(-)
>
> Maxime,
>
> Do do want the individual submaintainers to take these? Or, send one
> branch to Arnd and Olof? I'm fine with either one as any merge
> conflicts should be trivial.
I don't have a strong opinion on this one, I guess both will be fine.
Arnd, Olof, what do you prefer?
I'll probably have to send a v2 anyway, I forgot to remove the include
of the irqchip headers.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-05-13 15:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 9:43 [PATCH 00/14] Cleanup irqchip_init calls Maxime Ripard
2013-05-13 9:44 ` [PATCH 01/14] ARM: sunxi: Remove init_irq declaration in machine description Maxime Ripard
2013-05-13 9:44 ` [PATCH 02/14] ARM: zynq: " Maxime Ripard
2013-05-13 9:44 ` [PATCH 03/14] ARM: nomadik: " Maxime Ripard
2013-05-13 9:44 ` [PATCH 04/14] ARM: picoxcell: " Maxime Ripard
2013-05-13 9:44 ` [PATCH 05/14] ARM: shmobile: " Maxime Ripard
2013-05-14 0:35 ` Simon Horman
2013-05-14 8:23 ` Maxime Ripard
2013-05-13 9:44 ` [PATCH 06/14] ARM: bcm281xx: " Maxime Ripard
2013-05-13 20:06 ` Christian Daudt
2013-05-14 8:25 ` Maxime Ripard
2013-05-14 14:58 ` Christian Daudt
2013-05-13 9:44 ` [PATCH 07/14] ARM: spear: " Maxime Ripard
2013-05-13 9:46 ` Viresh Kumar
2013-05-13 9:44 ` [PATCH 08/14] ARM: msm: " Maxime Ripard
2013-05-13 18:26 ` David Brown
2013-05-14 8:32 ` Maxime Ripard
2013-05-13 9:44 ` [PATCH 09/14] ARM: mvebu: " Maxime Ripard
2013-05-13 15:19 ` Jason Cooper
2013-05-13 15:53 ` Maxime Ripard [this message]
2013-05-13 17:09 ` Olof Johansson
2013-05-13 9:44 ` [PATCH 10/14] ARM: mxs: " Maxime Ripard
2013-05-13 9:44 ` [PATCH 11/14] ARM: sirf: " Maxime Ripard
2013-05-14 9:17 ` Barry Song
2013-05-13 9:44 ` [PATCH 12/14] ARM: vexpress: " Maxime Ripard
2013-05-13 12:35 ` Pawel Moll
2013-05-13 9:44 ` [PATCH 13/14] ARM: virt: " Maxime Ripard
2013-05-13 9:44 ` [PATCH 14/14] ARM: vt8500: " Maxime Ripard
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=51910C81.5050501@free-electrons.com \
--to=maxime.ripard@free-electrons.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).