alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Brian Austin <brian.austin@cirrus.com>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: [PATCH RESEND v2 3/4] ASoC: cs42l52: convert pdata config to regmap_update_bits
Date: Fri, 25 Oct 2013 16:43:02 +0100	[thread overview]
Message-ID: <20131025154302.GC26122@sirena.org.uk> (raw)
In-Reply-To: <1382713277-10306-4-git-send-email-brian.austin@cirrus.com>


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

On Fri, Oct 25, 2013 at 10:01:16AM -0500, Brian Austin wrote:
> Moving platform data to bus probe and convert to regmap_update_bits.
> This will work nicer when converted to device tree instead of having it
> split into multiple probes

Applied, thanks.

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

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



  reply	other threads:[~2013-10-25 15:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 15:01 [PATCH RESEND v2 0/4] Cleanups/Bugfixes and DT Prep for CS42L52 Brian Austin
2013-10-25 15:01 ` [PATCH RESEND v2 1/4] ASoC: cs42l52: Add platform data for reset gpio Brian Austin
2013-10-25 15:42   ` Mark Brown
2013-10-25 15:01 ` [PATCH RESEND v2 2/4] ASoC: cs42l52: increase MAX_REGISTER for regmap_register_patch Brian Austin
2013-10-25 15:37   ` Mark Brown
2013-10-25 17:49     ` Brian Austin
2013-10-25 20:22       ` Mark Brown
2013-10-25 20:36         ` Brian Austin
2013-10-25 20:26       ` Brian Austin
2013-10-25 15:01 ` [PATCH RESEND v2 3/4] ASoC: cs42l52: convert pdata config to regmap_update_bits Brian Austin
2013-10-25 15:43   ` Mark Brown [this message]
2013-10-25 15:01 ` [PATCH RESEND v2 4/4] ASoC: cs42l52: Add chip rev id message Brian Austin
2013-10-25 15:43   ` Mark Brown

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=20131025154302.GC26122@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=brian.austin@cirrus.com \
    --cc=lgirdwood@gmail.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;
as well as URLs for NNTP newsgroup(s).