notmuch/test/corpora/lkml/cur/1382298793.002688:2,

95 lines
4.4 KiB
Text
Raw Normal View History

From: Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 44/44] sound/soc/codecs: Remove unnecessary
semicolons
Date: Mon, 15 Nov 2010 19:34:07 +0000
Lines: 16
Message-ID: <20101115193407.GK12986@rakim.wolfsonmicro.main>
References: <cover.1289789604.git.joe@perches.com>
<97fd199b7dac50613f6843156687223928cce44a.1289789605.git.joe@perches.com>
<20101115134939.GC12986@rakim.wolfsonmicro.main>
<1289840957.16461.138.camel@Joe-Laptop>
<20101115173031.GI12986@rakim.wolfsonmicro.main>
<1289842444.16461.140.camel@Joe-Laptop>
<20101115182708.GJ12986@rakim.wolfsonmicro.main>
<1289845830.16461.149.camel@Joe-Laptop>
<20101115190738.GF3338@sirena.org.uk>
<1289848458.16461.150.camel@Joe-Laptop>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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,
Ian Lartey <ian@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
To: Joe Perches <joe@perches.com>
X-From: alsa-devel-bounces@alsa-project.org Mon Nov 15 20:34:23 2010
Return-path: <alsa-devel-bounces@alsa-project.org>
Envelope-to: glad-alsa-devel-2@m.gmane.org
Received: from alsa0.perex.cz ([212.20.107.51])
by lo.gmane.org with esmtp (Exim 4.69)
(envelope-from <alsa-devel-bounces@alsa-project.org>)
id 1PI4oo-0008LE-En
for glad-alsa-devel-2@m.gmane.org; Mon, 15 Nov 2010 20:34:22 +0100
Received: by alsa0.perex.cz (Postfix, from userid 1000)
id 9B9BF24551; Mon, 15 Nov 2010 20:34:21 +0100 (CET)
X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mail1.perex.cz
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled
version=3.2.4
Received: from alsa0.perex.cz (localhost [127.0.0.1])
by alsa0.perex.cz (Postfix) with ESMTP id 7F6F424547;
Mon, 15 Nov 2010 20:34:16 +0100 (CET)
X-Original-To: alsa-devel@alsa-project.org
Delivered-To: alsa-devel@alsa-project.org
Received: by alsa0.perex.cz (Postfix, from userid 1000)
id 4D4F724548; Mon, 15 Nov 2010 20:34:14 +0100 (CET)
Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com
[80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 9C6502453F
for <alsa-devel@alsa-project.org>; Mon, 15 Nov 2010 20:34:09 +0100 (CET)
Received: from rakim.wolfsonmicro.main (lumison.wolfsonmicro.com
[87.246.78.27])
by opensource2.wolfsonmicro.com (Postfix) with ESMTPSA id 992AA788028;
Mon, 15 Nov 2010 19:34:08 +0000 (GMT)
Received: from broonie by rakim.wolfsonmicro.main with local (Exim 4.72)
(envelope-from <broonie@rakim.wolfsonmicro.main>)
id 1PI4oZ-0005Qk-Q4; Mon, 15 Nov 2010 19:34:07 +0000
Content-Disposition: inline
In-Reply-To: <1289848458.16461.150.camel@Joe-Laptop>
X-Cookie: I like your SNOOPY POSTER!!
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: alsa-devel@alsa-project.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Alsa-devel mailing list for ALSA developers -
http://www.alsa-project.org" <alsa-devel.alsa-project.org>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
<mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
<mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Sender: alsa-devel-bounces@alsa-project.org
Errors-To: alsa-devel-bounces@alsa-project.org
Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/1062713>
On Mon, Nov 15, 2010 at 11:14:18AM -0800, Joe Perches wrote:
> On Mon, 2010-11-15 at 19:07 +0000, Mark Brown wrote:
> > I'd suggest using pattern matching to look up the
> > rules for generating the prefixes (it's pretty much entirely prefixes)
> > in the same way you're handling figuring out who to mail - that'd
> > probably cover it in an automatable fashion.
> Publish a tool that works and I'll use it.
It appears your scripts are already hooked into get_maintainers.pl which
would seem the obvious place to do this? Sadly I don't do perl, though
it looks like you're doing pretty much all the work on that anyway.
The main thing here is to avoid your patches sticking out - as well as
the hassle applying them stuff like this is also a red flag on review.