linux-kernel - Re: [PATCH 0/3] Try out the irqdomain + generic chip integration series

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.LFD.2.02.1305291017070.2995@ionos>
Date:	Wed, 29 May 2013 10:19:37 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Grant Likely <grant.likely@...aro.org>
cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Try out the irqdomain + generic chip integration
 series

Grant,

On Wed, 29 May 2013, Grant Likely wrote:

> Hi Thomas,
> 
> Rather than just straight reviewing the generic irq chip patch series, I
> tried it out by converting another driver to use it. As far as I've been
> able to tell it does the right thing and you can have my ack. The first
> patch in this series adds another feature needed by the versatile
> driver. Patch 2 should be okay, but I'd like to get an ack from Ben
> before it gets applied.

I pick up #1 and push it with the other lot, so people can start
working on top of that. I'll put it into a separate branch
(irq/for-arm) so SoC folks can grab it from there to avoid inter tree
dependencies.
 
> I need to get someone to test patch 3 on hardware before you pick up
> that one.

Sure. It might also go through the SoC tree(s).
 
> Oh, and I'll reply directly to patch 7 of your series with an ack and a
> minor comment.

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/