From: Pavel Machek <pavel@ucw.cz>
To: Joe Perches <joe@perches.com>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
alsa-devel@alsa-project.org, Jiri Kosina <trivial@kernel.org>,
Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Ian Lartey <ian@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 44/44] sound/soc/codecs: Remove unnecessary semicolons
Date: Wed, 17 Nov 2010 20:32:56 +0100 [thread overview]
Message-ID: <20101117193256.GA28010@ucw.cz> (raw)
In-Reply-To: <1289842444.16461.140.camel@Joe-Laptop>
On Mon 2010-11-15 09:34:04, Joe Perches wrote:
> On Mon, 2010-11-15 at 17:30 +0000, Mark Brown wrote:
> > On Mon, Nov 15, 2010 at 09:09:17AM -0800, Joe Perches wrote:
> > > Signed-off-by: Joe Perches <joe@perches.com>
> > Applied, thanks.
> > Please try to use changelog formats consistent with the code you're
> > modifying.
>
> I think it's more important to use consistent changelogs
> for a patch series.
And I agree here. Having to learn code-style quirks for patches is
bad, having to learn new changelog style for each subsystem is very
bad.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-11-17 19:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 3:04 [PATCH 00/44] remove unnecessary semicolons Joe Perches
2010-11-15 3:05 ` [PATCH 43/44] sound/core/pcm_lib.c: Remove " Joe Perches
2010-11-22 6:44 ` Takashi Iwai
2010-11-15 3:05 ` [PATCH 44/44] sound/soc/codecs: " Joe Perches
2010-11-15 11:09 ` Liam Girdwood
2010-11-15 13:49 ` Mark Brown
2010-11-15 17:09 ` Joe Perches
2010-11-15 17:30 ` Mark Brown
2010-11-15 17:34 ` Joe Perches
2010-11-15 18:27 ` Mark Brown
2010-11-15 18:30 ` Joe Perches
2010-11-15 19:07 ` Mark Brown
2010-11-15 19:14 ` Joe Perches
2010-11-15 19:34 ` Mark Brown
2010-11-15 19:52 ` Joe Perches
2010-11-16 10:49 ` Mark Brown
2010-11-16 14:51 ` rfc: rewrite commit subject line for subsystem maintainer preference tool Joe Perches
2010-11-16 15:04 ` Mark Brown
2010-11-16 17:37 ` Florian Mickler
2010-11-16 18:12 ` Mark Brown
2010-11-16 19:35 ` Florian Mickler
2010-11-16 19:55 ` Mark Brown
2010-11-16 20:21 ` Randy Dunlap
2010-11-16 20:42 ` Joe Perches
2010-11-16 20:46 ` Randy Dunlap
2010-11-16 23:22 ` Mark Brown
2010-11-16 23:28 ` Randy Dunlap
2010-11-16 23:50 ` Mark Brown
2010-11-16 23:57 ` Joe Perches
2010-11-17 0:55 ` Randy Dunlap
2010-11-16 23:57 ` Joe Perches
2010-11-16 23:01 ` Mark Brown
2010-11-17 0:44 ` Stefan Richter
2010-11-17 0:53 ` Jiri Kosina
2010-11-17 17:07 ` Mark Brown
2010-11-17 21:07 ` Stefan Richter
2010-11-17 23:49 ` Joe Perches
2010-11-17 19:32 ` Pavel Machek [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=20101117193256.GA28010@ucw.cz \
--to=pavel@ucw.cz \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=ian@opensource.wolfsonmicro.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=tiwai@suse.de \
--cc=trivial@kernel.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 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).