From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Harald Geyer <harald-95f8Dae0BrPYtjvyW6yDsg@public.gmane.org>
Cc: Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH,RESEND2] regulator: fixed, gpio: dt: regulator-name is required property
Date: Wed, 14 Feb 2018 10:42:35 +0000 [thread overview]
Message-ID: <20180214104235.GA9804@sirena.org.uk> (raw)
In-Reply-To: <E1eltrI-0000Kv-W3-rvrRdOlaWMmli2aaYNgTVBW+3FKk/ZpWT2auq/jSWdo@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
On Wed, Feb 14, 2018 at 11:00:12AM +0100, Harald Geyer wrote:
> Mark Brown writes:
> > 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 ...
Which just boils down to a "what's going on with this" message.
> > 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.
No, I'm saying don't send pings at all. Resend patches if you think
they've got lost, and as normal when you're sending a patch it should
start off a new thread. The goal is to send something that can be
directly acted on when it's seen rather than requring another round of
mails.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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: Wed, 14 Feb 2018 10:42:35 +0000 [thread overview]
Message-ID: <20180214104235.GA9804@sirena.org.uk> (raw)
In-Reply-To: <E1eltrI-0000Kv-W3@stardust.g4.wien.funkfeuer.at>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
On Wed, Feb 14, 2018 at 11:00:12AM +0100, Harald Geyer wrote:
> Mark Brown writes:
> > 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 ...
Which just boils down to a "what's going on with this" message.
> > 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.
No, I'm saying don't send pings at all. Resend patches if you think
they've got lost, and as normal when you're sending a patch it should
start off a new thread. The goal is to send something that can be
directly acted on when it's seen rather than requring another round of
mails.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-02-14 10:42 UTC|newest]
Thread overview: 12+ 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 14:43 ` Harald Geyer
2018-02-13 15:45 ` Mark Brown
[not found] ` <20180213154530.GF5988-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-02-14 10:00 ` Harald Geyer
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 [this message]
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-14 16:28 ` 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
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=20180214104235.GA9804@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=harald-95f8Dae0BrPYtjvyW6yDsg@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.