From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755410Ab3JIPPb (ORCPT ); Wed, 9 Oct 2013 11:15:31 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:27880 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754443Ab3JIPP1 (ORCPT ); Wed, 9 Oct 2013 11:15:27 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 50.131.214.131 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19RjS0pTv8DEzVlOYB8169o Date: Wed, 9 Oct 2013 08:15:23 -0700 From: Tony Lindgren To: Roger Quadros Cc: bcousson@baylibre.com, balbi@ti.com, linux-usb@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 5/6] Revert "ARM: OMAP2+: Provide alias to USB PHY clock" Message-ID: <20131009151522.GA8313@atomide.com> References: <1381226799-29158-1-git-send-email-rogerq@ti.com> <1381226799-29158-6-git-send-email-rogerq@ti.com> <52550180.1000506@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52550180.1000506@ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Roger Quadros [131009 00:19]: > Hi Tony, > > On 10/08/2013 01:06 PM, Roger Quadros wrote: > > This reverts commit 741532c4a995be11815cb72d4d7a48f442a22fea. > > > > The proper clock reference is provided in device tree so we > > no longer need this. > > Could you please Ack this one? I think it is best if it goes through Benoit's tree. I could queue this into my board removal series that will be based on Benoit's branch if that works for you. And this also seems to depend on the omap-for-v3.13/quirk branch that moves all the legacy pdata handling into pdata-quirks.c. The reason for this is that we want to keep the .dts changes completely separate from the code changes to avoid dependencies that cause pointless merge conflicts. And the .dts files will be moved to live in a separate repo soonish, so it's good to be prepared for that. Regards, Tony