From: Mark Brown <broonie@kernel.org>
To: Kevin Cernekee <cernekee@chromium.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
dgreid@chromium.org, Andrew Bresticker <abrestic@chromium.org>,
Olof Johansson <olofj@chromium.org>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 3/5] ASoC: tas571x: Add DT binding document
Date: Wed, 6 May 2015 00:01:43 +0100 [thread overview]
Message-ID: <20150505230143.GQ15510@sirena.org.uk> (raw)
In-Reply-To: <CAJzqFtaRd7GN6af=7jZSh01mL04XBFYE5cGfHY9V=p7uKFwf_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
On Tue, May 05, 2015 at 03:56:09PM -0700, Kevin Cernekee wrote:
> Note that the regcache changes were intentionally ordered before the
> tas571x commits, because the regcache changes are needed for the new
> driver to work correctly. In the for-next branch I see the tas571x
> commits, but not the regcache changes.
That's fine, there's no actual code dependency and the regmap git tree
is separate to the ASoC git tree. It's not like there's an existing
driver we'd be breaking the bisection for.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-05 23:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 22:14 [PATCH V4 0/5] tas571x amplifier driver Kevin Cernekee
2015-05-05 22:14 ` [PATCH V4 1/5] regmap: Add a helper function for regcache sync test Kevin Cernekee
2015-05-06 12:01 ` Mark Brown
2015-05-05 22:14 ` [PATCH V4 2/5] regmap: Use regcache_mark_dirty() to indicate power loss or reset Kevin Cernekee
2015-05-06 12:01 ` Mark Brown
2015-05-05 22:14 ` [PATCH V4 3/5] ASoC: tas571x: Add DT binding document Kevin Cernekee
2015-05-05 22:32 ` Mark Brown
2015-05-05 22:56 ` Kevin Cernekee
2015-05-05 23:01 ` Mark Brown [this message]
2015-05-05 22:14 ` [PATCH V4 4/5] ASoC: tas571x: New driver for TI TAS571x power amplifiers Kevin Cernekee
2015-05-05 22:14 ` [PATCH V4 5/5] MAINTAINERS: Add entry for tas571x ASoC codec driver Kevin Cernekee
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=20150505230143.GQ15510@sirena.org.uk \
--to=broonie@kernel.org \
--cc=abrestic@chromium.org \
--cc=alsa-devel@alsa-project.org \
--cc=cernekee@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@chromium.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@chromium.org \
/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®