From: Greg Dietsche <gregory.dietsche@cuw.edu>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: perex@perex.cz, tiwai@suse.de,
broonie@opensource.wolfsonmicro.com,
dp@opensource.wolfsonmicro.com, lrg@ti.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wm8940: remove unecessary if statement
Date: Mon, 06 Jun 2011 15:58:54 -0500 [thread overview]
Message-ID: <4DED3F8E.60400@cuw.edu> (raw)
In-Reply-To: <4DECD0B1.4010802@cam.ac.uk>
Hi Jonathan,
On 06/06/2011 08:05 AM, Jonathan Cameron wrote:
> On 06/06/11 13:45, Greg Dietsche wrote:
>
>
>>> Also if you want to do this sort of cleanup, please also fix the
>>> equivalent in wm8940_resume and wm8940_add_widgets. Ack is for
>>> what is here, plus those if you do them.
>>>
>>>
I updated the patch to include these too.
>>> Just as an aside, there is no earthly point in cc'ing lkml for a
>>> simple cleanup like this. Just adds to already huge amount of noise!
>>>
>>>
...and remove LKML from the CC list... :)
> Fair enough. The posting to lkml makes more sense now I know it came
> out of coccinelle (I guess with a load of others? - if so convention would be
>
a handful... not too many, but it sounds like if my semantic patch were
to be improved,
there might be a few more.
> to put them all in a series cc'ing the relevant lists / maintainers for individual
> patches in the series - that way everyone knows what is going on).
>
> If it is an individual patch like this, then use apply common sense. It makes
> no functional changes + is well within a subsystem with it's own active mailing
> list. It needs to be sent somewhere publicly, but in this case
> I'd say alsa-devel is the right destination. The only people who are even going
> to read this are the subsystem maintainer, the driver author or the chronically
> bored.
>
> Also I think convention is to have the script somewhere (cover letter to that
> series perhaps?). See the other series people have done with coccinelle and
> how they handled this.
>
>
Thanks so much for the great explanation being patient with a kernel
newbie :)
Greg
prev parent reply other threads:[~2011-06-06 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 0:47 [PATCH] wm8940: remove unecessary if statement Greg Dietsche
2011-06-06 9:31 ` Jonathan Cameron
2011-06-06 9:51 ` Liam Girdwood
2011-06-06 9:51 ` Liam Girdwood
2011-06-06 20:53 ` [PATCH v2] wm8940: remove unnecessary if statements Greg Dietsche
2011-06-07 8:01 ` Jonathan Cameron
2011-06-07 8:33 ` Liam Girdwood
2011-06-07 8:48 ` Mark Brown
2011-06-06 12:45 ` [PATCH] wm8940: remove unecessary if statement Greg Dietsche
2011-06-06 13:05 ` Jonathan Cameron
2011-06-06 20:58 ` Greg Dietsche [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=4DED3F8E.60400@cuw.edu \
--to=gregory.dietsche@cuw.edu \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@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.