From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Joe Perches <joe@perches.com>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] sound: max98090: Remove executable bit
Date: Wed, 20 Mar 2013 17:36:27 +0100 [thread overview]
Message-ID: <20130320163627.GS28775@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1363792936.16270.30.camel@joe-AO722>
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
On Wed, Mar 20, 2013 at 08:22:16AM -0700, Joe Perches wrote:
> On Wed, 2013-03-20 at 10:57 +0100, Mark Brown wrote:
> > I've applied this but I'm fed up to the back teeth of having to hand
> > edit trivial patches from you because you ignore the subject line styles
> > of subsystems and make up your own.
> Your style rules just don't matter to me and
> you can ignore the patches and fix it yourself.
> Or better, create a tool for others to use that
> follow your silly style rules.
This is just like any other coding style thing - you should be creating
patches that look like other patches for the affected, if there's things
like obvious visual differences in what you're doing you're doing it
wrong.
Automation doesn't work for things like this, there's a good solid
reason why there's generally a human involved in patch; the other people
who submit lots of cleanups generally manage to figure this out
usefully, you might want to discuss techniques with them.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-03-20 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 21:58 [PATCH] sound: max98090: Remove executable bit Joe Perches
2013-03-20 9:57 ` Mark Brown
2013-03-20 15:22 ` Joe Perches
2013-03-20 16:36 ` Mark Brown [this message]
2013-03-20 22:54 ` Joe Perches
2013-03-21 16:25 ` Mark Brown
2013-03-21 17:16 ` Joe Perches
2013-03-21 17:44 ` Mark Brown
2013-03-21 17:44 ` Mark Brown
2013-03-21 17:53 ` Joe Perches
2013-03-21 18:44 ` Mark Brown
2013-03-21 18:44 ` Mark Brown
2013-03-21 19:16 ` Joe Perches
2013-03-21 19:16 ` Joe Perches
2013-03-21 20:37 ` Mark Brown
2013-03-21 20:40 ` Joe Perches
2013-03-21 21:26 ` Mark Brown
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=20130320163627.GS28775@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=joe@perches.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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.