[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUWKMrRoNL-vBpnAPPCdnJXRnOjJuQW9m7nJ3emjyOVOZQ@mail.gmail.com>
Date: Thu, 6 Sep 2012 02:22:22 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Randy Dunlap <rdunlap@...otime.net>
Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
alsa-devel@...a-project.org
Subject: Re: [PATCH -next] soc: fix wm0010.c printk format warning
On Thu, Sep 6, 2012 at 2:11 AM, Randy Dunlap <rdunlap@...otime.net> wrote:
> On 09/05/2012 05:06 PM, Mark Brown wrote:
>
>> On Wed, Sep 05, 2012 at 04:24:57PM -0700, Randy Dunlap wrote:
>>> From: Randy Dunlap <rdunlap@...otime.net>
>>>
>>> Fix printk format warning:
>>
>> Somone already sent this. As ever please try to use subject lines
>> appropriate for the subsystem. Please also consider who you're CCing -
>
>
> Unfortunately the MAINTAINERS file does not tell me what to include
> in the $subject line for the subsystem.
> What would you like to see there, please? Maybe ASoC?
>
git log --oneline sound/soc/codecs/wm0010.c
Label looks like "ASoC: wm0010:"... (ASoC kills my shift key, I would
like to see all labels lower-case).
>> there's no need to copy -next on things like this which aren't
>
>
> I have always done a reply-to-all for linux-next patches, so after
> a few years someone days Don't Do That (IYO).
>
Then maintainers should check compiler-warnings in their area - regularly?
$ grep warning: v3.6.0-rc4-next20120905-1-iniza-generic/deb-pkg.log |
grep 'sound/soc' | wc -l
10
I agree that breakage and regressions should be dealt with higher
priority... Such patches like this should be welcome, anyway.
>> integration issues for example, if we start doing that then it'd get
>> drowned in noise from all the development.
>
>
> Agreed, many of us are already drowning from 1000+ emails per day.
> (seriously)
>
Spam will one day eliminate Email, it's perverted.
- Sedat -
> --
> ~Randy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists