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>
Subject: Re: [PATCH,RESEND] regulator: fixed, gpio: dt: regulator-name is required property
Date: Tue, 13 Feb 2018 12:01:11 +0000 [thread overview]
Message-ID: <20180213120111.GC5988@sirena.org.uk> (raw)
In-Reply-To: <E1elZ6B-0000M8-99-rvrRdOlaWMmli2aaYNgTVBW+3FKk/ZpWT2auq/jSWdo@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Tue, Feb 13, 2018 at 12:50:09PM +0100, Harald Geyer wrote:
> what happened to the patch below? It was written to your specification,
> got an ACK from devicetree and has no unaddressed review comments, so I
> can't see what might be holding it back.
>
> It has been more then 6 month since the last resend, but I still can't
> find it in any tree...
Please don't send content free pings. Sending content free pings adds
to the mail volume (if they are seen at all) which is often the problem
and since they can't be reviewed directly if something has gone wrong
you'll have to resend the patches anyway, though there are some other
maintainers who like them - if in doubt look at how patches for the
subsystem are normally handled.
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-02-13 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 8:36 [PATCH,RESEND] regulator: fixed, gpio: dt: regulator-name is required property Harald Geyer
[not found] ` <1498293410-16222-1-git-send-email-harald-95f8Dae0BrPYtjvyW6yDsg@public.gmane.org>
2018-02-13 11:50 ` Harald Geyer
[not found] ` <E1elZ6B-0000M8-99-rvrRdOlaWMmli2aaYNgTVBW+3FKk/ZpWT2auq/jSWdo@public.gmane.org>
2018-02-13 12:01 ` Mark Brown [this message]
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=20180213120111.GC5988@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=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 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).