From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756137Ab3AUPDF (ORCPT ); Mon, 21 Jan 2013 10:03:05 -0500 Received: from utopia.booyaka.com ([74.50.51.50]:36556 "EHLO utopia.booyaka.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753296Ab3AUPDE (ORCPT ); Mon, 21 Jan 2013 10:03:04 -0500 Date: Mon, 21 Jan 2013 15:03:02 +0000 (UTC) From: Paul Walmsley To: Roger Quadros cc: sameo@linux.intel.com, balbi@ti.com, tony@atomide.com, kishon@ti.com, sshtylyov@mvista.com, bjorn@mork.no, linux@arm.linux.org.uk, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Rajendra Nayak , Benoit Cousson , Mike Turquette Subject: Re: [PATCH v8 19/22] ARM: OMAP3: clock data: get rid of unused USB host clock aliases and dummies In-Reply-To: <50FD0BEF.9000007@ti.com> Message-ID: References: <1358511445-26656-1-git-send-email-rogerq@ti.com> <1358511445-26656-20-git-send-email-rogerq@ti.com> <50FD0BEF.9000007@ti.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On Mon, 21 Jan 2013, Roger Quadros wrote: > On 01/18/2013 10:27 PM, Paul Walmsley wrote: > > On Fri, 18 Jan 2013, Roger Quadros wrote: > > > >> We don't need multiple aliases for the OMAP USB host clocks and neither > >> the dummy clocks so remove them. > >> > >> CC: Paul Walmsley > >> CC: Rajendra Nayak > >> CC: Benoit Cousson > >> CC: Mike Turquette > >> > >> Signed-off-by: Roger Quadros > >> Reviewed-by: Felipe Balbi > >> Acked-by: Paul Walmsley > > > > Per Tony's earlier request, you can drop this patch and patch 20 from your > > series now. I've got them queued for 3.10 or late 3.9 merge window. > > > > Should have mentioned it earlier, but just this patch without the rest > of the cleanup patches will break USB Host on OMAP3, as the old driver > bails out if optional clock nodes are missing. > > Including patch 20 doesn't seem to cause a problem with OMAP4 though. I've got these two patches queued for merging after your other patches go upstream -- e.g., probably 3.10. Do you foresee any problems with that? - Paul