linux-kernel - Re: [alsa-devel] [PATCH] ASoC: fsl_asrc: constify snd_soc_dai

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170713161056.Horde.jVvECgjHYS4t4jiD4hqm2WC@gator4166.hostgator.com>
Date:   Thu, 13 Jul 2017 16:10:56 -0500
From:   "Gustavo A. R. Silva" <garsilva@...eddedor.com>
To:     Joe Perches <joe@...ches.com>
Cc:     Mark Brown <broonie@...nel.org>, 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 Joe,

Quoting Joe Perches <joe@...ches.com>:

> On Thu, 2017-07-13 at 10:18 -0500, Gustavo A. R. Silva wrote:
>> 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. :)
>
> 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.

I ended up following your suggestions:

https://lkml.org/lkml/2017/7/13/739 (Notice that these are new  
patches. Not related to the ones I previously sent)

Much appreciated
Thanks!
--
Gustavo A. R. Silva