From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [alsa-devel] [PATCH] ASoC: fsl_asrc: constify snd_soc_dai_ops structure Date: Fri, 14 Jul 2017 04:08:21 -0700 Message-ID: <1500030501.4457.70.camel@perches.com> References: <20170713072351.GA1485@embeddedgus> <20170713101630.odml56qmsvgxqj64@sirena.org.uk> <20170713101814.Horde.q8OhHejhvSALVEt2o11aUTW@gator4166.hostgator.com> <1499969891.4457.59.camel@perches.com> <20170714110233.fqkmgy7kyhje7mfy@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170714110233.fqkmgy7kyhje7mfy@sirena.org.uk> Sender: linux-kernel-owner@vger.kernel.org To: Mark Brown Cc: "Gustavo A. R. Silva" , Takashi Iwai , Timur Tabi , Nicolin Chen , Xiubo Li , Fabio Estevam , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org List-Id: alsa-devel@alsa-project.org 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.