From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tim Gardner <tim.gardner@canonical.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Liam Girdwood <lgirdwood@gmail.com>, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org
Subject: Re: [PATCH linux-next v2] ASoC: adau1373: adau1373_hw_params: Silence overflow warning
Date: Tue, 12 Mar 2013 19:39:41 +0000 [thread overview]
Message-ID: <20130312193940.GF19942@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <513F7F46.3050200@canonical.com>
[-- Attachment #1.1: Type: text/plain, Size: 844 bytes --]
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.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tim Gardner <tim.gardner@canonical.com>
Cc: linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
device-drivers-devel@blackfin.uclinux.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH linux-next v2] ASoC: adau1373: adau1373_hw_params: Silence overflow warning
Date: Tue, 12 Mar 2013 19:39:41 +0000 [thread overview]
Message-ID: <20130312193940.GF19942@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <513F7F46.3050200@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-12 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 17:34 [PATCH] ASoC: adau1373: adau1373_hw_params: Silence overflow warning Tim Gardner
2013-03-11 10:01 ` Lars-Peter Clausen
2013-03-11 15:37 ` Tim Gardner
2013-03-11 18:55 ` Lars-Peter Clausen
2013-03-11 19:18 ` [PATCH linux-next v2] " Tim Gardner
2013-03-11 19:26 ` Lars-Peter Clausen
2013-03-12 18:47 ` Mark Brown
2013-03-12 18:47 ` Mark Brown
2013-03-12 19:17 ` Tim Gardner
2013-03-12 19:39 ` Mark Brown [this message]
2013-03-12 19:39 ` 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=20130312193940.GF19942@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.com \
--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.