From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Eric Millbrandt <emillbrandt@dekaresearch.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patch@alsa-project.org" <patch@alsa-project.org>
Subject: Re: [PATCH 1/1] Do not write to invalid registers on the wm9712.
Date: Wed, 23 Dec 2009 15:23:19 +0000 [thread overview]
Message-ID: <20091223152319.GA2474@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD308C08371C3@dekaexchange07.deka.local>
On Wed, Dec 23, 2009 at 10:00:37AM -0500, Eric Millbrandt wrote:
> It looks like the legal jargon post-pended to the patch creates grief for
> git. I am resubmitting the patch as an attachment so that is will not get
> mangled.
Applied, thanks. The signature won't have done anything to affect the
patch - the unified diff format can handle comments and other descriptive
text interspersed with the code without problems.
prev parent reply other threads:[~2009-12-23 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 17:28 [PATCH 1/1] Do not write to invalid registers on the wm9712 Eric Millbrandt
2009-12-22 17:59 ` Liam Girdwood
2009-12-22 23:46 ` Mark Brown
2009-12-23 15:00 ` Eric Millbrandt
2009-12-23 15:23 ` 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=20091223152319.GA2474@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=emillbrandt@dekaresearch.com \
--cc=grant.likely@secretlab.ca \
--cc=patch@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.