From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: cw00.choi@samsung.com, alsa-devel@alsa-project.org,
myungjoo.ham@samsung.com, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] switch: arizona: Clear trig_sts bits on all paths
Date: Wed, 7 Aug 2013 12:23:16 +0100 [thread overview]
Message-ID: <20130807112316.GS1302@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130807100313.GW6427@sirena.org.uk>
On Wed, Aug 07, 2013 at 11:03:13AM +0100, Mark Brown wrote:
> This isn't an ASoC patch, it should be CCed to lkml. Might want to
> update the subject line too.
Oops yeah sorry about that will respin.
Thanks,
Charles
prev parent reply other threads:[~2013-08-07 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 8:28 [PATCH] switch: arizona: Clear trig_sts bits on all paths Charles Keepax
2013-08-07 10:03 ` Mark Brown
2013-08-07 11:23 ` Charles Keepax [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=20130807112316.GS1302@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.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).