[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191008165230.GR4382@sirena.co.uk>
Date: Tue, 8 Oct 2019 17:52:30 +0100
From: Mark Brown <broonie@...nel.org>
To: Ladislav Michl <ladis@...ux-mips.org>
Cc: YueHaibing <yuehaibing@...wei.com>, m.felsch@...gutronix.de,
alsa-devel@...a-project.org, ckeepax@...nsource.cirrus.com,
kuninori.morimoto.gx@...esas.com, linux-kernel@...r.kernel.org,
piotrs@...nsource.cirrus.com, andradanciu1997@...il.com,
lgirdwood@...il.com, paul@...pouillou.net,
Hulk Robot <hulkci@...wei.com>, shifu0704@...ndersoft.com,
enric.balletbo@...labora.com, srinivas.kandagatla@...aro.org,
tiwai@...e.com, mirq-linux@...e.qmqm.pl,
rf@...nsource.wolfsonmicro.com
Subject: Re: [alsa-devel] Applied "ASoc: tas2770: Fix build error without
GPIOLIB" to the asoc tree
On Tue, Oct 08, 2019 at 06:35:08PM +0200, Ladislav Michl wrote:
> Hmm, too late it seems...
> Patch should actually remove <linux/gpio.h> as this is legacy one (see comment
> on the top and also Documentation/driver-api/gpio/consumer.rst)
Yes, leaving that is an oversight.
> And that brings a question. Given this is -next only is it actually possible
> to squash fixes into 1a476abc723e ("tas2770: add tas2770 smart PA kernel driver")
> just to make bisect a bit more happy?
No:
> > 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.
Apart from anything else I've merged up the fixes branch IIRC which
causes trouble.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists