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: <20130508123902.GL7478@sirena.org.uk>
Date:	Wed, 8 May 2013 13:39:02 +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 01:03:26PM +0100, Lee Jones wrote:

> Besides, I was more referencing the massively increased effort
> imparted to the developer by applying patches in an arbitrary order.
> Forcing the developer to rearranging and rebase the patch-set causing
> unnecessary merge conflicts. It's better if the maintainer takes the
> patch-set in the order it was written to prevent unnecessary (which is
> the key word here) such things.

Meh, rebase takes care of all this stuff for you and you really need to
be rebasing anyway to take account of changes sent by other people.  The
problem you were having was that you weren't rebasing at all.

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