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:	Sat, 9 Feb 2013 18:42:19 -0800
From:	Olof Johansson <olof@...om.net>
To:	Linus Walleij <linus.walleij@...ricsson.com>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Stephen Warren <swarren@...dia.com>,
	Anmar Oueja <anmar.oueja@...aro.org>,
	Lee Jones <lee.jones@...aro.org>, arm@...nel.org,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH 11/14] ARM: ux500: remove irq_base property from
 platform_data

On Tue, Feb 05, 2013 at 08:48:32PM +0100, Linus Walleij wrote:
> From: Lee Jones <lee.jones@...aro.org>
> 
> AB8500 GPIO no longer handles its GPIO IRQs. Instead, the AB8500
> core driver has taken back the responsibility. Prior to this
> happening, the AB8500 GPIO driver provided a set of virtual IRQs
> which were used as a pass-through. These virtual IRQs had a base
> of MOP500_AB8500_VIR_GPIO_IRQ_BASE, which was passed though pdata.
> We don't need to do this anymore, so we're pulling out the
> property from the structure.
> 
> Cc: arm@...nel.org
> Signed-off-by: Lee Jones <lee.jones@...aro.org>
> Signed-off-by: Linus Walleij <linus.walleij@...aro.org>
> ---
> Requesting an ACK from the ARM SoC maintainers on this patch.

This patch on its own doesn't apply cleanly at all to arm-soc, I'm guessing
because I need the rest of the series. With the presumption that you're not
going to cause grief from sfr due to excessive conflicts. I.e. please try
merging with arm-soc for-next to see how bad it is:

patch 11-14:

Acked-by: Olof Johansson <olof@...om.net>

If it's conflict-heavy, we'll stage a topic branch that we can both
pull in.  I'm guessing/hoping that won't be the case though.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ