From: Mark Brown <broonie@kernel.org>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: YueHaibing <yuehaibing@huawei.com>,
m.felsch@pengutronix.de, alsa-devel@alsa-project.org,
ckeepax@opensource.cirrus.com, kuninori.morimoto.gx@renesas.com,
linux-kernel@vger.kernel.org, piotrs@opensource.cirrus.com,
andradanciu1997@gmail.com, lgirdwood@gmail.com,
paul@crapouillou.net, Hulk Robot <hulkci@huawei.com>,
shifu0704@thundersoft.com, enric.balletbo@collabora.com,
srinivas.kandagatla@linaro.org, tiwai@suse.com,
mirq-linux@rere.qmqm.pl, rf@opensource.wolfsonmicro.com
Subject: Re: [alsa-devel] Applied "ASoc: tas2770: Fix build error without GPIOLIB" to the asoc tree
Date: Tue, 8 Oct 2019 17:52:30 +0100 [thread overview]
Message-ID: <20191008165230.GR4382@sirena.co.uk> (raw)
In-Reply-To: <20191008163508.GA16283@lenoch>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-10-08 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 7:22 [PATCH -next] ASoc: tas2770: Fix build error without GPIOLIB YueHaibing
2019-10-06 9:57 ` [alsa-devel] " Ladislav Michl
2019-10-06 10:06 ` Yuehaibing
2019-10-06 10:46 ` [PATCH v2 " YueHaibing
2019-10-06 15:31 ` mirq-linux
2019-10-06 19:12 ` Ladislav Michl
2019-10-07 13:03 ` Applied "ASoc: tas2770: Fix build error without GPIOLIB" to the asoc tree Mark Brown
2019-10-08 16:35 ` [alsa-devel] " Ladislav Michl
2019-10-08 16:52 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191008165230.GR4382@sirena.co.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andradanciu1997@gmail.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=enric.balletbo@collabora.com \
--cc=hulkci@huawei.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=ladis@linux-mips.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=mirq-linux@rere.qmqm.pl \
--cc=paul@crapouillou.net \
--cc=piotrs@opensource.cirrus.com \
--cc=rf@opensource.wolfsonmicro.com \
--cc=shifu0704@thundersoft.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
--cc=yuehaibing@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®