linux-kernel - RE: [PATCH] arm/tegra: add support for tegra30 interrupts

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]

Date:	Wed, 2 Nov 2011 11:06:58 -0700
From:	Stephen Warren <swarren@...dia.com>
To:	Peter De Schrijver <pdeschrijver@...dia.com>
CC:	Colin Cross <ccross@...roid.com>, Olof Johansson <olof@...om.net>,
	Russell King <linux@....linux.org.uk>,
	Gary King <gking@...dia.com>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] arm/tegra: add support for tegra30 interrupts

Stephen Warren wrote at Wednesday, November 02, 2011 10:39 AM:
> Peter De Schrijver wrote by Wednesday, November 02, 2011 9:38 AM:
> > Tegra30 has 1 extra legacy interrupt controller. Use the GIC ITLinesNumber
> > field to determine how many interrupt controllers we have and initialize
> > appropriately. Also make room for the extra tegra30 interrupts by moving
> > the GPIO IRQ base. This shouldn't affect existing code as it determines the
> > correct IRQ number for GPIOs using TEGRA_GPIO_TO_IRQ()
> >
> > Signed-off-by: Peter De Schrijver <pdeschrijver@...dia.com>
> 
> After fixing one small issue I comment on below,
> Acked-by: Stephen Warren <swarren@...dia.com>

Also, both this and "arm/tegra: remove unused defines":

Tested-by: Stephen Warren <swarren@...dia.com>

(on Tegra20 Seaboard/Springbank, not on Tegra30 Cardhu)

-- 
nvpublic

--
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/