[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170713101814.Horde.q8OhHejhvSALVEt2o11aUTW@gator4166.hostgator.com>
Date: Thu, 13 Jul 2017 10:18:14 -0500
From: "Gustavo A. R. Silva" <garsilva@...eddedor.com>
To: Mark Brown <broonie@...nel.org>
Cc: 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
Hi Mark,
Quoting Mark Brown <broonie@...nel.org>:
> On Thu, Jul 13, 2017 at 09:32:41AM +0200, Takashi Iwai wrote:
>
>> please stop posting in this style. It's really annoying to see
>> spontaneously popping-up almost same patch for more than two hours
>> long.
>
>> If you have a series of the same fix patches, send them as a patch
>> set in a shot with a thread. git-send-email does it right.
>
>> I don't mind a couple of patches posted separately, but this is over
>> the limit.
>
> Or at least just collect them up and send them all at one time even if
> not as a single thread (you don't want to CC everyone affected by a
> single patch in the set on everything, that's harder to avoid when
> sending a series via git, but it can be confusing to get one item in a
> large patch series without context).
I like this idea better. I will do so next time. :)
Thank you
--
Gustavo A. R. Silva
Powered by blists - more mailing lists