[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151006095715.GF12635@sirena.org.uk>
Date: Tue, 6 Oct 2015 10:57:15 +0100
From: Mark Brown <broonie@...nel.org>
To: David Miller <davem@...emloft.net>
Cc: jon@...gle.org, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/2] regmap: Allow installing custom
reg_update_bits function
On Mon, Oct 05, 2015 at 11:21:48PM -0700, David Miller wrote:
> > Ugh, this is a mess :( Can you please drop this patch instead?
> I can't just "drop" changes. Once a commit hits my tree it is part
> of the permanent record.
I was expecting a revert if you want to keep the branch fast forward
only.
> The easiest thing to do is to send a relative fix, and that's why
> I have asked for exactly that.
This isn't very good for reviewing the API change, and of course I'd
also expect this change to be in the regmap tree so we can work on
regmap without collisions, I obviously can't just merge in net-next.
I was thinking about making some further changes on top of this and it
*is* fiddling about in the core.
Jon, please send me a patch against the regmap tree for review while we
work out how to sort out this mess.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists