From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932120Ab2AIVhY (ORCPT ); Mon, 9 Jan 2012 16:37:24 -0500 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:38562 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755770Ab2AIVhX (ORCPT ); Mon, 9 Jan 2012 16:37:23 -0500 Date: Mon, 9 Jan 2012 21:37:21 +0000 From: Mark Brown To: Samuel Ortiz Cc: Sangbeom Kim , lrg@ti.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4] regulator: Add S5M8767A regulator driver Message-ID: <20120109213721.GD30766@opensource.wolfsonmicro.com> References: <1325225153-32389-1-git-send-email-sbkim73@samsung.com> <20120108231657.GD13679@sortiz-mobl> <20120109064703.GT29065@opensource.wolfsonmicro.com> <20120109090821.GK13679@sortiz-mobl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120109090821.GK13679@sortiz-mobl> X-Cookie: You look tired. User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 09, 2012 at 10:08:21AM +0100, Samuel Ortiz wrote: > On Sun, Jan 08, 2012 at 10:47:04PM -0800, Mark Brown wrote: > > I've not reviwed it yet and there should be no dependency on the MFD > > tree so no need to merge it via that - the fact that there's a Kconfig > > dependency on the MFD means that the two can get merged in any order. > Not only a Kconfig dependency, but also the regulator driver including some of > the headers defined in the mfd patch: > +#include > +#include > So, both need to get merged at the same time. No, the point is that the Kconfig dependency means that the code dependency isn't an issue - the code won't actually get built until the MFD driver is merged. But anyway it looks like the regulator will have slipped to 3.4 so the MFD will already be in.