linux-kernel - Re: [PATCH -next] soc: fix wm0010.c printk format warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5047EA1C.7080608@xenotime.net>
Date:	Wed, 05 Sep 2012 17:11:08 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	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 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?

> 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).

> 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)

-- 
~Randy
--
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/