linux-kernel - Re: [PATCH linux-next v2] ASoC: adau1373: adau1373_hw

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] [day] [month] [year] [list]

Message-ID: <20130312193940.GF19942@opensource.wolfsonmicro.com>
Date:	Tue, 12 Mar 2013 19:39:41 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Tim Gardner <tim.gardner@...onical.com>
Cc:	linux-kernel@...r.kernel.org, Lars-Peter Clausen <lars@...afoo.de>,
	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	device-drivers-devel@...ckfin.uclinux.org,
	alsa-devel@...a-project.org
Subject: Re: [PATCH linux-next v2] ASoC: adau1373: adau1373_hw_params:
 Silence overflow warning

On Tue, Mar 12, 2013 at 01:17:26PM -0600, Tim Gardner wrote:

> > threads (I nearly deleted this unread) and avoid including

> > enormous CC lists like this in the body of the mail.

> I'm just going by the default output of scripts/get_maintainer.pl. Are
> there better options to filter the roles ? In this case I received a
> review from a supporter (Lars), and the patch is being committed by
> yet another supporter (yourself). Would you have noticed this patch
> had I restricted the Cc list to just maintainers and lists ?

I specifically mean don't include the lists in the body of the mail - it
means they either litter the git log or need to be manually deleted.  If
you're just using unfiltered get_maintainer output then I'd suggest that
you generate the CCs in your scripts when sending rather than putting
them in the changelog.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)