linux-kernel - Re: [PATCH 2/2] ARM: remove mach .init_irq for irqchip

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130328124228.GA29616@verge.net.au>
Date:	Thu, 28 Mar 2013 21:42:28 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc:	Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
	Russell King <linux@....linux.org.uk>,
	linux-arm-kernel@...ts.infradead.org,
	David Brown <davidb@...eaurora.org>,
	Daniel Walker <dwalker@...o99.com>,
	Bryan Huntsman <bryanh@...eaurora.org>,
	Alessandro Rubini <rubini@...pv.it>,
	Linus Walleij <linus.walleij@...aro.org>,
	STEricsson <STEricsson_nomadik_linux@...t.st.com>,
	Jamie Iles <jamie@...ieiles.com>,
	Barry Song <baohua.song@....com>,
	Magnus Damm <magnus.damm@...il.com>,
	Michal Simek <michal.simek@...inx.com>,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	linux-sh@...r.kernel.org
Subject: Re: [PATCH 2/2] ARM: remove mach .init_irq for irqchip_init users

On Thu, Mar 28, 2013 at 10:41:44AM +0100, Maxime Ripard wrote:
> Now that the arm core code calls irqchip_init, we can remove it from all
> the machines that were using it.
> 
> Signed-off-by: Maxime Ripard <maxime.ripard@...e-electrons.com>
> ---
>  arch/arm/mach-bcm/board_bcm.c                  |    1 -
>  arch/arm/mach-msm/board-dt-8660.c              |    1 -
>  arch/arm/mach-msm/board-dt-8960.c              |    1 -
>  arch/arm/mach-nomadik/cpu-8815.c               |    1 -
>  arch/arm/mach-picoxcell/common.c               |    1 -
>  arch/arm/mach-prima2/common.c                  |    1 -
>  arch/arm/mach-shmobile/board-kzm9g-reference.c |    1 -
>  arch/arm/mach-shmobile/setup-emev2.c           |    1 -
>  arch/arm/mach-shmobile/setup-sh73a0.c          |    1 -
>  arch/arm/mach-spear/spear1310.c                |    1 -
>  arch/arm/mach-spear/spear1340.c                |    1 -
>  arch/arm/mach-spear/spear300.c                 |    1 -
>  arch/arm/mach-spear/spear310.c                 |    1 -
>  arch/arm/mach-spear/spear320.c                 |    1 -
>  arch/arm/mach-spear/spear6xx.c                 |    1 -
>  arch/arm/mach-vexpress/v2m.c                   |    1 -
>  arch/arm/mach-virt/virt.c                      |    1 -
>  arch/arm/mach-zynq/common.c                    |    1 -
>  18 files changed, 18 deletions(-)

mach-shmobile portion:

Acked-by: Simon Horman <horms+renesas@...ge.net.au>

I have some new users of this queued up for v3.10.
How should we handle that?

In particular:

arch/arm/mach-shmobile/setup-r8a73a4.c
arch/arm/mach-shmobile/intc-r8a7779.c
arch/arm/mach-shmobile/setup-r8a7778.c

You can find these in the renesas-next-20130328 tag of
my renesas tree on kernel.org. They are or will soon
be in linux-next.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/