[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160831160227.GC5967@sirena.org.uk>
Date: Wed, 31 Aug 2016 17:02:27 +0100
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee.jones@...aro.org>
Cc: Tero Kristo <t-kristo@...com>, Dave Gerlach <d-gerlach@...com>,
Keerthy <j-keerthy@...com>, tony@...mide.com,
devicetree@...r.kernel.org, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, russ.dill@...com, robh+dt@...nel.org,
mark.rutland@....com, linux@...linux.org.uk
Subject: Re: Applied "mfd: tps65218: add version check to the PMIC probe" to
the regulator tree
On Wed, Aug 31, 2016 at 03:50:18PM +0100, Lee Jones wrote:
> On Wed, 31 Aug 2016, Mark Brown wrote:
> > You acked it, that's saying that you're OK with the patch and are
> > expecting someone else to apply it.
> No it doesn't, you made that up. :)
> I know when you and some others Ack a patch, that's what you mean, but
That's the standard meaning I'm afraid, you're going to confuse people
if you do that. I'd suggest using a different tag if you want to do
this, probably make one up.
> you've been working with me for long enough to know that's not what I
> mean when I Ack a patch. I do it as an indication that I've reviewed
> the patch and I'm happy with it. Most MFD patches that have
Sorry but I'm not actually reading most of these threads, I've not seen
this behaviour. Mostly I just look at the relevant patches, especially
on the resends where presumably this has been happening. Not sure why I
even saw the ack here, perhaps I had some question about the versioning
API.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists