All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] sound/soc/atmel: don't use devm_pinctrl_get_select_default() in probe
Date: Thu, 17 Oct 2013 18:46:14 +0200	[thread overview]
Message-ID: <20131017164331.GA2896@katana> (raw)
In-Reply-To: <20131014163753.GF2443@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]


> > > Applied, thanks.  Please use subject lines appropriate to the subsystem.
> 
> > That's quite a nut to crack with a generated patch series running over
> > the whole tree. I wonder if it is really worth the effort?
> 
> I think it's probably worth the effort to add something to put rules for
> these things in MAINTAINERS, it'd cover 90% of cases.  If you're sending
> only one of a big series with a subject line that won't pattern match
> that's a good way to get stuff dropped on the floor.

On the other hand, MAINTAINERS information gets overlooked and/or could
get stale. Thinking about it again, it is probably less work (at least
for me with i2c) to create a git-hook fixing the subject line than to
always nag people.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] sound/soc/atmel: don't use devm_pinctrl_get_select_default() in probe
Date: Thu, 17 Oct 2013 18:46:14 +0200	[thread overview]
Message-ID: <20131017164331.GA2896@katana> (raw)
In-Reply-To: <20131014163753.GF2443@sirena.org.uk>


> > > Applied, thanks.  Please use subject lines appropriate to the subsystem.
> 
> > That's quite a nut to crack with a generated patch series running over
> > the whole tree. I wonder if it is really worth the effort?
> 
> I think it's probably worth the effort to add something to put rules for
> these things in MAINTAINERS, it'd cover 90% of cases.  If you're sending
> only one of a big series with a subject line that won't pattern match
> that's a good way to get stuff dropped on the floor.

On the other hand, MAINTAINERS information gets overlooked and/or could
get stale. Thinking about it again, it is probably less work (at least
for me with i2c) to create a git-hook fixing the subject line than to
always nag people.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131017/e0b8d265/attachment.sig>

  reply	other threads:[~2013-10-17 16:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-13 16:17 [PATCH 0/4] remove devm_pinctrl_get_select_default from drivers Wolfram Sang
2013-10-13 16:17 ` Wolfram Sang
2013-10-13 16:17 ` [PATCH 1/4] drivers/gpu/drm/tilcdc: don't use devm_pinctrl_get_select_default() in probe Wolfram Sang
2013-10-13 16:17   ` Wolfram Sang
2013-10-13 16:17 ` [PATCH 2/4] drivers/mmc/host: " Wolfram Sang
2013-10-13 16:17   ` Wolfram Sang
2013-10-14  7:28   ` Romain Izard
2013-10-14  7:28     ` Romain Izard
2013-10-13 16:17 ` [PATCH 3/4] drivers/pwm: " Wolfram Sang
2013-10-13 16:17   ` Wolfram Sang
2013-10-15 10:17   ` Thierry Reding
2013-10-15 10:17     ` Thierry Reding
2013-10-22  7:39   ` Thierry Reding
2013-10-22  7:39     ` Thierry Reding
2013-10-13 16:17 ` [PATCH 4/4] sound/soc/atmel: " Wolfram Sang
2013-10-13 16:17   ` Wolfram Sang
2013-10-13 16:17   ` Wolfram Sang
2013-10-14  5:28   ` Bo Shen
2013-10-14  5:28     ` Bo Shen
2013-10-14  5:28     ` Bo Shen
2013-10-14 13:17   ` Mark Brown
2013-10-14 13:17     ` Mark Brown
2013-10-14 13:17     ` Mark Brown
2013-10-14 14:56     ` Wolfram Sang
2013-10-14 14:56       ` Wolfram Sang
2013-10-14 16:37       ` Mark Brown
2013-10-14 16:37         ` Mark Brown
2013-10-17 16:46         ` Wolfram Sang [this message]
2013-10-17 16:46           ` Wolfram Sang
2013-10-17 17:42           ` Mark Brown
2013-10-17 17:42             ` 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=20131017164331.GA2896@katana \
    --to=wsa@the-dreams.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.