[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1500030501.4457.70.camel@perches.com>
Date: Fri, 14 Jul 2017 04:08:21 -0700
From: Joe Perches <joe@...ches.com>
To: Mark Brown <broonie@...nel.org>
Cc: "Gustavo A. R. Silva" <garsilva@...eddedor.com>,
Takashi Iwai <tiwai@...e.de>, Timur Tabi <timur@...i.org>,
Nicolin Chen <nicoleotsuka@...il.com>,
Xiubo Li <Xiubo.Lee@...il.com>,
Fabio Estevam <fabio.estevam@....com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: fsl_asrc: constify snd_soc_dai_ops
structure
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.
Powered by blists - more mailing lists