From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752212AbdLFMqu (ORCPT <rfc822;w@1wt.eu>);
        Wed, 6 Dec 2017 07:46:50 -0500
Received: from heliosphere.sirena.org.uk ([172.104.155.198]:56226 "EHLO
        heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751544AbdLFMqq (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 6 Dec 2017 07:46:46 -0500
Date: Wed, 6 Dec 2017 12:46:38 +0000
From: Mark Brown <broonie@kernel.org>
To: "Andrew F. Davis" <afd@ti.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>, Rob Herring <robh+dt@kernel.org>,
        Mark Rutland <mark.rutland@arm.com>,
        =?iso-8859-1?Q?Beno=EEt?= Cousson <bcousson@baylibre.com>,
        Tony Lindgren <tony@atomide.com>, alsa-devel@alsa-project.org,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 08/19] ASoC: tlv320aic31xx: Switch GPIO handling to
 use gpiod_* API
Message-ID: <20171206124638.GD1827@finisterre>
References: <20171129213300.20021-1-afd@ti.com>
 <20171129213300.20021-9-afd@ti.com>
 <537c8d62-de11-15e8-11bc-08e8334d4322@ti.com>
 <17fcc926-9ee8-1229-ea3d-f38347cb9a23@ti.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="DiL7RhKs8rK9YGuF"
Content-Disposition: inline
In-Reply-To: <17fcc926-9ee8-1229-ea3d-f38347cb9a23@ti.com>
X-Cookie: Semper Fi, dude.
User-Agent: Mutt/1.9.1 (2017-09-22)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


--DiL7RhKs8rK9YGuF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Dec 05, 2017 at 03:23:49PM -0600, Andrew F. Davis wrote:
> On 12/04/2017 10:47 AM, Andrew F. Davis wrote:

> > Kbuild bot seems mad a this one, looks like I need to include
> > linux/gpio/consumer.h, will fix for v3.

> Looks like you already have this in your -next branch, how do you want
> this fix, I can send a delta patch with the added include, a new v3
> version that you can replace the patch in-tree with, or if it's easier
> for you manually fix in-tree?

As the patch applied mail says:

| If any updates are required or you are submitting further changes they
| should be sent as incremental updates against current git, existing
| patches will not be replaced.

--DiL7RhKs8rK9YGuF
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlon5q0ACgkQJNaLcl1U
h9B6Vwf+Mim1FuDiJAqRFw5C3aCj84xUEoCjBY3Cm39RFdpTANw0nH9p5+GJa7DB
8mspachRVyVILrexXPyWnpr1WGW0YSdNU+ZJPfh5qjg79mt8F4ELo7HKyl3LHN3x
OLa8G0z/gTJ9oQNfeb8kzU77nEiA8/eUU33CVr6pQEyHpde2XF+Fvvsl3FqCB7Jt
I07tR1FHbO14+RqrVeY778lOy8jAXzxYhMfMR14iPA+GeuwlkZ9uQmWxE7y0Dwyt
RLehl/4UoJuJWM1TNBEoSLwvW0tBeap/tHvu1240gwx0dHVZzi+XhUZWVq+5z/ul
gGcVKLBbq4Hp8r+IdZp+cMmU5fCB7A==
=ZRtc
-----END PGP SIGNATURE-----

--DiL7RhKs8rK9YGuF--