From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <liam.r.girdwood@intel.com>
Subject: Re: [PATCH 2/4] mfd: wm5102: Map in additional FLL control registers
Date: Thu, 11 Apr 2013 18:22:11 +0100 [thread overview]
Message-ID: <20130411172211.GT9243@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130408162223.GC24058@zurbaran>
[-- Attachment #1.1: Type: text/plain, Size: 455 bytes --]
On Mon, Apr 08, 2013 at 06:22:23PM +0200, Samuel Ortiz wrote:
> Hi Mark,
>
> On Wed, Mar 06, 2013 at 02:28:14PM +0800, Mark Brown wrote:
> > Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > ---
> > drivers/mfd/wm5102-tables.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> Did you merge this patchset through the ASoC tree ?
Yes, let me know if that's a problem and I can back stuff out but it
seemed sensible.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-04-11 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1362551296-14920-1-git-send-email-broonie@opensource.wolfsonmicro.com>
2013-03-06 6:28 ` [PATCH 2/4] mfd: wm5102: Map in additional FLL control registers Mark Brown
[not found] ` <20130408162223.GC24058@zurbaran>
2013-04-11 17:22 ` Mark Brown [this message]
2013-03-06 6:28 ` [PATCH 3/4] ASoC: arizona: Increase FLL synchroniser bandwidth for high frequencies Mark Brown
2013-03-06 6:28 ` [PATCH 4/4] ASoC: arizona: Optimise FLL loop gains 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=20130411172211.GT9243@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@intel.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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