linux-kernel - Re: [RFT][PATCH 1/2] regulator: ab8500: Fix build error

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] [day] [month] [year] [list]

Date:	Tue, 19 Feb 2013 12:04:04 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Axel Lin <axel.lin@...ics.com>,
	Bengt Jonsson <bengt.g.jonsson@...ricsson.com>,
	Mattias WALLIN <mattias.wallin@...ricsson.com>,
	Emeric Vigier <emeric.vigier@...ricsson.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFT][PATCH 1/2] regulator: ab8500: Fix build error

On Mon, Feb 18, 2013 at 10:24:21AM +0000, Lee Jones wrote:

> The patches which caused the issues addressed by this patch-set have
> since been rewritten. I have subsequently requested that Mark deletes
> the AB8500 for-next branch. We're going to start again after this
> merge window.

So, as discussed you really shouldn't have done that - unless there's a
very serious problem you should be assuming that patches that have been
applied are going to stay applied and working from the latest upstream
tree.  Once something is in -next the expectation is that it's going to
be sent during the next merge window.  As well as the issues with
maintainers getting fed up having to look at the same code over and over
again it causes people like Axel to waste their time.

However I am probably going to just throw away the current ab8500 work
this time.  Please resend your patches after the merge window (which
just opened).

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