Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Harald Geyer <harald@ccbib.org>
To:     Mark Brown <broonie@kernel.org>
cc:     Liam Girdwood <lgirdwood@gmail.com>, devicetree@vger.kernel.org,
        Rob Herring <robh@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH,RESEND2] regulator: fixed, gpio: dt: regulator-name is required property
In-reply-to: <20180213154530.GF5988@sirena.org.uk>
References: <1518532988-10990-1-git-send-email-harald@ccbib.org> <20180213154530.GF5988@sirena.org.uk>
Comments: In-reply-to Mark Brown <broonie@kernel.org>
   message dated "Tue, 13 Feb 2018 15:45:30 +0000."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1295.1518602412.1@stardust.g4.wien.funkfeuer.at>
Date:   Wed, 14 Feb 2018 11:00:12 +0100
Message-Id: <E1eltrI-0000Kv-W3@stardust.g4.wien.funkfeuer.at>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Mark Brown writes:
> On Tue, Feb 13, 2018 at 02:43:08PM +0000, Harald Geyer wrote:
> 
> > BTW, it took me a bit to figure out that by "content free ping" you are
> > refering to the quoting of the patch. Maybe you can reword your canned
> > response to make it easier to understand.
> 
> No, a content free ping is when you just send a reply saying something
> to the effect of "hey, what's going on with this?".

Well, I did quote the entire patch and gave a summary of the status
as far as I know it. So I really don't understand why I got the
"no content free pings" response ...

> As I said in my
> reply best case the answer is going to be "I have no idea, you need to
> resend since I'll need the patch to do anything with it" and worst case
> it just won't get seen at all if the thing really did get buried
> somehow.

So you are saying you don't want pings as followups to patches at all, if
the patch is old enough that it probably got lost?

I guess that would make sense too, but again it's not obvious to read
the canned response that way.