linux-kernel - Re: [PATCHv2 00/20] Cleanup 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: <51949646.4000107@free-electrons.com>
Date:	Thu, 16 May 2013 10:18:14 +0200
From:	Maxime Ripard <maxime.ripard@...e-electrons.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Michal Simek <michal.simek@...inx.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Jamie Iles <jamie@...ieiles.com>,
	Simon Horman <horms@...ge.net.au>,
	Magnus Damm <magnus.damm@...il.com>,
	Christian Daudt <csd@...adcom.com>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	David Brown <davidb@...eaurora.org>,
	Jason Cooper <jason@...edaemon.net>,
	Andrew Lunn <andrew@...n.ch>,
	Gregory Clement <gregory.clement@...e-electrons.com>,
	Shawn Guo <shawn.guo@...aro.org>,
	Barry Song <baohua.song@....com>,
	Tony Prisk <linux@...sktech.co.nz>,
	linux-arm-kernel@...ts.infradead.org, linux-sh@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	Olof Johansson <olof@...om.net>
Subject: Re: [PATCHv2 00/20] Cleanup irqchip_init calls

Hi Arnd,

Le 15/05/2013 14:55, Arnd Bergmann a écrit :
> On Tuesday 14 May 2013, Maxime Ripard wrote:
>> This is a splitted up version of the patch I previously sent to
>> remove the explicit declaration of irqchip_init as the init_irq callback in
>> the machine descriptions.
>>
>> Since it was a pretty tricky patch to merge, since it was touching a lot of
>> different platforms, I splitted it for each platforms, and rebased it on top
>> of 3.10-rc1.
>>
>> The best way to merge it is probably that each one of us take into their tree
>> the patches that are relevant for our architecture and send them to arm-soc
>> later on.
> 
> Sounds good to me. I'm sure that some platform maintainers will fail to
> apply this though. Could you send whatever remains as a separate branch
> in a couple of weeks so we can directly apply it to next/cleanup?

Ok, I will.

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
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/