From: Michael Opdenacker <michael.opdenacker@linaro.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: jarkko.nikula@bitmer.com, lrg@ti.com, perex@perex.cz,
tiwai@suse.de, linux-omap@vger.kernel.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] omap: sound: fix checkpatch.pl error
Date: Mon, 10 Oct 2011 15:03:27 +0200 [thread overview]
Message-ID: <4E92ED1F.9020902@linaro.org> (raw)
In-Reply-To: <20111010093240.GB3040@opensource.wolfsonmicro.com>
Hi Mark,
On 10/10/2011 11:32 AM, Mark Brown wrote:
> Applied, but please do try to make sure your changelogs resemble those
> for the rest of the subsystem. Especially for trivial patches it's not
> good to increase the effort required to apply them.
Thanks! I will use "ASoC" in my commit messages if I understand correctly.
I must confess I didn't pay enough attention to the list of recipients,
which I just got from scripts/get_maintainer.pl.
I will be more careful next time.
Thanks again,
Michael.
--
Michael Opdenacker - Community Manager
Linaro, http://linaro.org
Cell: +33 621 604 642
IRC: 'opm' in #linaro on irc.freenode.net
prev parent reply other threads:[~2011-10-10 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 5:07 [PATCH 0/2] omap: sound: style and warning fixes Michael Opdenacker
2011-10-10 5:07 ` [PATCH 1/2] omap: sound: fix "ambiguous else" warning Michael Opdenacker
2011-10-10 6:54 ` Jarkko Nikula
2011-10-10 7:38 ` Michael Opdenacker
2011-10-10 5:07 ` [PATCH 2/2] omap: sound: fix checkpatch.pl error Michael Opdenacker
2011-10-10 6:56 ` Jarkko Nikula
2011-10-10 6:56 ` Jarkko Nikula
2011-10-10 9:32 ` Mark Brown
2011-10-10 13:03 ` Michael Opdenacker [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=4E92ED1F.9020902@linaro.org \
--to=michael.opdenacker@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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.