From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755717Ab2HOTXm (ORCPT ); Wed, 15 Aug 2012 15:23:42 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:50148 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755509Ab2HOTXi (ORCPT ); Wed, 15 Aug 2012 15:23:38 -0400 Message-ID: <502BF734.9000608@wwwdotorg.org> Date: Wed, 15 Aug 2012 13:23:32 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Tony Prisk CC: vt8500-wm8505-linux-kernel@googlegroups.com, linux-fbdev@vger.kernel.org, Mark Brown , Grant Likely , Russell King , rtc-linux@googlegroups.com, Florian Tobias Schandinat , Alan Stern , Eric Andersson , linux-serial@vger.kernel.org, Arnd Bergmann , Hauke Mehrtens , devicetree-discuss@lists.ozlabs.org, Rob Herring , Stephen Warren , Neil Zhang , linux-arm-kernel@lists.infradead.org, Alan Cox , Alessandro Zummo , Linus Walleij , Greg Kroah-Hartman , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, Felipe Balbi , Rob Landley Subject: Re: [PATCHv2 0/8] *** ARM: Update arch-vt8500 to Devicetree *** References: <1344477300-25251-1-git-send-email-linux@prisktech.co.nz> In-Reply-To: <1344477300-25251-1-git-send-email-linux@prisktech.co.nz> X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/08/2012 07:54 PM, Tony Prisk wrote: > This patchset updates arch-vt8500 to devicetree and removes all the old-style > code. Support for WM8650 has also been added. Sorry for taking such a long time to re-review this. I scanned the series looking for just the changes to the issues I raised on v1, and I do see almost everything has been fixed up OK, except for the one issue I just commented on. So, aside from that, this series is fine by me. I'll defer to others about whether it's necessary to fix the display node-name-vs.-phandle issue I pointed out, or defer that until later.