linux-kernel - Re: [PATCH v2 2/6] ASoC: ux500: Do not clear state if already idle

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130509092825.GX7478@sirena.org.uk>
Date:	Thu, 9 May 2013 10:28:25 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Fabio Baltieri <fabio.baltieri@...aro.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
	Linus Walleij <linus.walleij@...aro.org>,
	Ola Lilja <ola.o.lilja@...ricsson.com>
Subject: Re: [PATCH v2 2/6] ASoC: ux500: Do not clear state if already idle

On Wed, May 08, 2013 at 03:06:18PM +0100, Lee Jones wrote:

> Bringing this back on subject, whilst trying not to drag this out for
> longer than we have to. I think replying to one's first patch with a
> subsequent version has its merits. And as long as the thread hasn't
> become too overgrown I see it as a useful tool to obtain an Ack or
> further comment easily and without churn overhead. This also aids in
> your quest to save maintainers from reviewing the same code
> repeatedly, as once the Ack is in place it's easy to see which patches
> are in need of further review and which ones can be skipped.

If you want to do that what often works better is to post an incremental
diff rather than the full patch to show exactly what's been done in the
fix.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)