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: <alpine.LFD.2.02.1303061058250.22263@ionos>
Date:	Wed, 6 Mar 2013 11:01:14 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Simon Horman <horms@...ge.net.au>
cc:	Magnus Damm <magnus.damm@...il.com>, linux-kernel@...r.kernel.org,
	linux-sh@...r.kernel.org, benh@...nel.crashing.org,
	grant.likely@...retlab.ca
Subject: Re: [PATCH] irqchip: Renesas INTC External IRQ pin driver

On Wed, 6 Mar 2013, Simon Horman wrote:
> On Mon, Feb 18, 2013 at 11:28:34PM +0900, Magnus Damm wrote:
> > The SoCs using this driver are currently mainly used
> > together with regular platform devices so this driver
> > allows configuration via platform data to support things
> > like static interrupt base address. DT support will
> > be added incrementally in the not so distant future.
> 
> Hi Thomas,
> 
> I'm wondering how you would like to handle merging this driver.
> I can think of three options but I'm sure there are others.
> 
> * You can take the patches (there is a follow-up series) yourself.
> * I can prepare a pull request for you
> * I can prepare a pull request for arm-soc with the shmobile patches that
>   enable the driver on the r8a7779 and sh73a0.
> 
> The last option is possibly the easiest.

Correct.

> But in that case I'd appreciate an Ack from you on this patch.

You want to pick the V2 series, which already has my blessing:

    https://lkml.org/lkml/2013/2/26/305

For merging it through arm-soc you have my ack now :)

Thanks,

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