From: Mark Brown <broonie@kernel.org>
To: Harald Geyer <harald@ccbib.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
Date: Tue, 13 Feb 2018 15:45:30 +0000 [thread overview]
Message-ID: <20180213154530.GF5988@sirena.org.uk> (raw)
In-Reply-To: <1518532988-10990-1-git-send-email-harald@ccbib.org>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
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?". 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. This is unfortunately something that happens upstream, things
fall through the cracks sometimes for various reasons (eg, if a new
patch gets sent in the middle of a thread sometimes it'll get deleted
along with the reset of the thread).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-02-13 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 14:43 [PATCH,RESEND2] regulator: fixed, gpio: dt: regulator-name is required property Harald Geyer
2018-02-13 15:45 ` Mark Brown [this message]
[not found] ` <20180213154530.GF5988-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-02-14 10:00 ` Harald Geyer
[not found] ` <E1eltrI-0000Kv-W3-rvrRdOlaWMmli2aaYNgTVBW+3FKk/ZpWT2auq/jSWdo@public.gmane.org>
2018-02-14 10:42 ` Mark Brown
2018-02-14 16:28 ` Applied "regulator: dt: regulator-name is required property" to the regulator tree Mark Brown
2018-02-15 9:39 ` Geert Uytterhoeven
[not found] ` <CAMuHMdVLO4Y-NzS6bLp2dUy1oSqmEthC_yD5jCe_R9H4vWBwMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-15 11:52 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180213154530.GF5988@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=harald@ccbib.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).