Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bard Liao <bardliao@realtek.com>
Cc: oder_chiou@realtek.com, alsa-devel@alsa-project.org,
	lars@metafoo.de, zhengxing@rock-chips.com, yang.a.fang@intel.com,
	lgirdwood@gmail.com, john.lin@realtek.com,
	koro.chen@mediatek.com, drinkcat@chromium.org, flove@realtek.com
Subject: Re: [PATCH v3 1/3] ASoC: rt5645: make RT5650_TDM_CTRL_4 readable
Date: Mon, 8 Jun 2015 19:27:42 +0100	[thread overview]
Message-ID: <20150608182742.GW14071@sirena.org.uk> (raw)
In-Reply-To: <20150608180925.GS14071@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 557 bytes --]

On Mon, Jun 08, 2015 at 07:09:25PM +0100, Mark Brown wrote:
> On Fri, Jun 05, 2015 at 01:24:15PM +0800, Bard Liao wrote:
> > Register RT5650_TDM_CTRL_4(0x7A) is readable and used for mixer
> > setting. It should be added in rt5645_readable_register function.
> 
> Applied all, thanks.

...then dropped as this seems to have lots of non-trivial conficts with
the fix/rt5645 branch.  Can you please check what's going on there and
resend?  Please use the tag I just sent to Takashi (asoc-v4.2) as the
thing to base your patches on for this resend.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2015-06-08 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05  5:24 [PATCH v3 1/3] ASoC: rt5645: make RT5650_TDM_CTRL_4 readable Bard Liao
2015-06-05  5:24 ` [PATCH v3 2/3] ASoC: rt5645: change gpio to gpiod APIs Bard Liao
2015-06-05  5:24 ` [PATCH v3 3/3] ASoC: rt5645: add device tree support Bard Liao
2015-06-08 18:09 ` [PATCH v3 1/3] ASoC: rt5645: make RT5650_TDM_CTRL_4 readable Mark Brown
2015-06-08 18:27   ` 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=20150608182742.GW14071@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=drinkcat@chromium.org \
    --cc=flove@realtek.com \
    --cc=john.lin@realtek.com \
    --cc=koro.chen@mediatek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=yang.a.fang@intel.com \
    --cc=zhengxing@rock-chips.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