From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751724AbdFHIqZ (ORCPT ); Thu, 8 Jun 2017 04:46:25 -0400 Received: from muru.com ([72.249.23.125]:50862 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751475AbdFHIqY (ORCPT ); Thu, 8 Jun 2017 04:46:24 -0400 Date: Thu, 8 Jun 2017 01:46:20 -0700 From: Tony Lindgren To: Ulf Hansson Cc: Kishon Vijay Abraham I , Rob Herring , Sekhar Nori , Russell King , linux-omap , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-mmc@vger.kernel.org" Subject: Re: [PATCH v2 0/8] omap*: Fixes/Cleanups for MMC devicetree node Message-ID: <20170608084619.GH3730@atomide.com> References: <20170607093749.15656-1-kishon@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.2 (2017-04-18) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Ulf Hansson [170608 00:24]: > If it helps, I can host a branch with the updates on the omap_hsmmc > driver, such it can be pulled in from arm soc? Great that works for me. Let's just make sure git bisect keeps working. > I guess you need that as, the DT changes relies on the new vqmmc > binding. Or you thing it doesn't matter, because for the current > changes that regulator is always an always on regulator? Or maybe we can just add the new regulator, then do a follow-up series to remove the old ones? Regards, Tony