From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753004AbcIAIVY (ORCPT ); Thu, 1 Sep 2016 04:21:24 -0400 Received: from mail-wm0-f42.google.com ([74.125.82.42]:36793 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751004AbcIAIVV (ORCPT ); Thu, 1 Sep 2016 04:21:21 -0400 Date: Thu, 1 Sep 2016 09:23:08 +0100 From: Lee Jones To: Mark Brown Cc: Tero Kristo , Dave Gerlach , Keerthy , tony@atomide.com, devicetree@vger.kernel.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, russ.dill@ti.com, robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk Subject: Re: Applied "mfd: tps65218: add version check to the PMIC probe" to the regulator tree Message-ID: <20160901082308.GF4921@dell> References: <1466412218-5906-8-git-send-email-j-keerthy@ti.com> <20160831083114.GP10121@dell> <20160831114105.GH3950@sirena.org.uk> <20160831145018.GO9415@dell> <20160831160227.GC5967@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160831160227.GC5967@sirena.org.uk> User-Agent: Mutt/1.6.2 (2016-07-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 31 Aug 2016, Mark Brown wrote: > 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. Reviewed-by-BUT-DONT-TAKE-IT-YOU-FIEND: :) Temporary-Acked-by-[to go through MFD tree]: Suggestions? > > 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. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog