From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Thomas Elste <thomas.elste-cSCHQGRfioA@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] regulator: tps65023: add device tree support
Date: Thu, 17 Sep 2015 10:20:15 +0100 [thread overview]
Message-ID: <20150917092015.GM11268@sirena.org.uk> (raw)
In-Reply-To: <20150917104335.5464f8b5@pluto>
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
On Thu, Sep 17, 2015 at 10:43:35AM +0200, Thomas Elste wrote:
> And I will use a separate patch for the binding document (just found
> Documentation/devicetree/bindings/submitting-patches.txt).
It's actually fine to just have them in the same patch for a simple
driver using established bindings like this - the DT maintainers are
unlikely to have the bandwidth to look at it anyway. But splitting is
also OK.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-17 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 13:33 tps65023: add device tree support Thomas Elste
[not found] ` <1442324035-16414-1-git-send-email-thomas.elste-cSCHQGRfioA@public.gmane.org>
2015-09-15 13:33 ` [PATCH] regulator: " Thomas Elste
[not found] ` <1442324035-16414-2-git-send-email-thomas.elste-cSCHQGRfioA@public.gmane.org>
2015-09-16 19:56 ` Mark Brown
[not found] ` <20150916195612.GT12027-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-09-17 8:43 ` Thomas Elste
2015-09-17 9:20 ` Mark Brown [this message]
2015-09-15 14:29 ` 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=20150917092015.GM11268@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=thomas.elste-cSCHQGRfioA@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