Re: [PATCH v7 0/5] mfd: tps65912: Driver rewrite with DT support

From: Mark Brown <broonie@kernel.org>
To: "Andrew F. Davis" <afd@ti.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/5] mfd: tps65912: Driver rewrite with DT support
Date: Tue, 8 Dec 2015 19:16:57 +0000	[thread overview]
Message-ID: <20151208191657.GA5727@sirena.org.uk> (raw)
In-Reply-To: <5665E4F7.1070707@ti.com>

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

On Mon, Dec 07, 2015 at 01:58:47PM -0600, Andrew F. Davis wrote:

> As all of this driver should be taken though the MFD tree how
> can this gpiolib change be handled? If we have gpio.parent it
> will not build on MFD, with gpio.dev it will fail to build when
> the changes are merged from the gpio subsystem. As the change
> has not been merged into linux-next as far a I can tell maybe
> this should be taken as is, then when the gpiolib change is
> made this can be changed with all the other drivers?

Do a cross tree merge in one direction or the other between MFD and GPIO.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]