From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: [PATCH] ASoC: fix documentation in soc-jack
Date: Tue, 9 Oct 2012 15:39:32 +0900 [thread overview]
Message-ID: <20121009063929.GP8237@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1349179699-8737-1-git-send-email-pmeerw@pmeerw.net>
On Tue, Oct 02, 2012 at 02:08:19PM +0200, Peter Meerwald wrote:
> From: Peter Meerwald <p.meerwald@bct-electronic.com>
>
> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
Applied, thanks. It would be helpful if your changelogs were, uh,
better documented :) - it does make life much easier when reviewing if
you've got an idea as to what's in the patch when you start reading it.
Something like "fixes spelling mistakes and mislabelled parameters" for
example.
prev parent reply other threads:[~2012-10-09 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 12:08 [PATCH] ASoC: fix documentation in soc-jack Peter Meerwald
2012-10-09 6:39 ` 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=20121009063929.GP8237@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=pmeerw@pmeerw.net \
/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).