From: Joe Perches <joe@perches•com>
To: Mark Brown <broonie@kernel•org>
Cc: "Gustavo A. R. Silva" <garsilva@embeddedor•com>,
Takashi Iwai <tiwai@suse•de>, Timur Tabi <timur@tabi•org>,
Nicolin Chen <nicoleotsuka@gmail•com>,
Xiubo Li <Xiubo.Lee@gmail•com>,
Fabio Estevam <fabio.estevam@nxp•com>,
Liam Girdwood <lgirdwood@gmail•com>,
Jaroslav Kysela <perex@perex•cz>, Takashi Iwai <tiwai@suse•com>,
alsa-devel@alsa-project•org, linuxppc-dev@lists•ozlabs.org,
linux-kernel@vger•kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: fsl_asrc: constify snd_soc_dai_ops structure
Date: Fri, 14 Jul 2017 04:08:21 -0700 [thread overview]
Message-ID: <1500030501.4457.70.camel@perches.com> (raw)
In-Reply-To: <20170714110233.fqkmgy7kyhje7mfy@sirena.org.uk>
On Fri, 2017-07-14 at 12:02 +0100, Mark Brown wrote:
> On Thu, Jul 13, 2017 at 11:18:11AM -0700, Joe Perches wrote:
>
> > I don't it's better.
> > It's not that confusing if the 0/n patch cover letter is cc'd
> > to all the appropriate mailing lists and all the [1..n]/n
> > patches are sent with in-reply-to of the cover letter and
> > send to the maintainers and appropriate mailing lists.
>
> With large serieses like Gustavo is sending the CC list can easily hit
> the points where mailing lists start blocking it, and the individual
> pathces really do need to go to the relevant people so they have sight
> of them.
I agree and that's what I wrote.
next prev parent reply other threads:[~2017-07-14 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 7:23 [PATCH] ASoC: fsl_asrc: constify snd_soc_dai_ops structure Gustavo A. R. Silva
2017-07-13 7:32 ` [alsa-devel] " Takashi Iwai
2017-07-13 7:36 ` Gustavo A. R. Silva
2017-07-13 10:16 ` Mark Brown
2017-07-13 15:18 ` Gustavo A. R. Silva
2017-07-13 18:18 ` Joe Perches
2017-07-13 21:10 ` Gustavo A. R. Silva
2017-07-14 11:02 ` Mark Brown
2017-07-14 11:08 ` Joe Perches [this message]
2017-07-14 11:25 ` Mark Brown
2017-07-17 4:22 ` Gustavo A. R. Silva
2017-07-17 16:05 ` Applied "ASoC: fsl_asrc: constify snd_soc_dai_ops structure" to the asoc tree 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=1500030501.4457.70.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=Xiubo.Lee@gmail$(echo .)com \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=fabio.estevam@nxp$(echo .)com \
--cc=garsilva@embeddedor$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=nicoleotsuka@gmail$(echo .)com \
--cc=perex@perex$(echo .)cz \
--cc=timur@tabi$(echo .)org \
--cc=tiwai@suse$(echo .)com \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox