From: Jonathan Cameron <jic23@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "milo.kim@ti.com" <milo.kim@ti.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"poeschel@lemonage.de" <poeschel@lemonage.de>,
"rnayak@ti.com" <rnayak@ti.com>,
Oleksandr Kozaruk <oleksandr.kozaruk@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"kishon@ti.com" <kishon@ti.com>,
"peter.ujfalusi@ti.com" <peter.ujfalusi@ti.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"jic23@cam.ac.uk" <jic23@cam.ac.uk>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"benoit.cousson@linaro.org" <benoit.cousson@linaro.org>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
"ch.naveen@samsung.com" <ch.n>
Subject: Re: [PATCH v8 0/2] TWL6030, TWL6032 GPADC driver
Date: Thu, 15 Aug 2013 12:03:02 +0100 [thread overview]
Message-ID: <520CB566.2050201@kernel.org> (raw)
In-Reply-To: <20130815091216.GB28366@e106331-lin.cambridge.arm.com>
>> The changes to the original driver:
>> - device tree adaptation;
>
> I couldn't see a binding document in this series or in mainline. Have I
> looked in the wrong places?
Nothing explicit supplied, but does it need one given it is doing only
iio bindings (bindings/iio/iio-bindings.txt)
plus twl child bindings
(bindings/mfd/twl-family.txt)
If it does, I guess absolutely everything does, then fair enough!
I guess that would make sense as there is no way for someone writing
a device tree to know that there is nothing else to be specified.
Thanks,
Jonathan
next prev parent reply other threads:[~2013-08-15 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 13:26 [PATCH v8 0/2] TWL6030, TWL6032 GPADC driver Oleksandr Kozaruk
2013-07-25 13:26 ` [PATCH v8 1/2] ARM: dts: twl: Add GPADC data to device tree Oleksandr Kozaruk
2013-07-25 13:26 ` [PATCH v8 2/2] iio: twl6030-gpadc: TWL6030, TWL6032 GPADC driver Oleksandr Kozaruk
[not found] ` <1374758813-6539-3-git-send-email-oleksandr.kozaruk-l0cyMroinI0@public.gmane.org>
2013-08-14 22:09 ` Jonathan Cameron
[not found] ` <CAPb7_mthhYXbp0tTKMvV=gwndfaHMxnrXPCgxUk3MSH1R+W9rQ@mail.gmail.com>
[not found] ` <CAPb7_mthhYXbp0tTKMvV=gwndfaHMxnrXPCgxUk3MSH1R+W9rQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-15 9:31 ` Jonathan Cameron
[not found] ` <1374758813-6539-1-git-send-email-oleksandr.kozaruk-l0cyMroinI0@public.gmane.org>
2013-08-15 9:12 ` [PATCH v8 0/2] " Mark Rutland
2013-08-15 11:03 ` Jonathan Cameron [this message]
2013-08-15 12:59 ` Mark Rutland
2013-08-15 17:59 ` Jonathan Cameron
[not found] ` <520D16EC.90604-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2013-08-16 6:39 ` Kozaruk, Oleksandr
2013-08-16 8:54 ` Mark Rutland
2013-08-16 12:48 ` Kozaruk, Oleksandr
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=520CB566.2050201@kernel.org \
--to=jic23@kernel.org \
--cc=benoit.cousson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@linaro.org \
--cc=jic23@cam.ac.uk \
--cc=kishon@ti.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=milo.kim@ti.com \
--cc=oleksandr.kozaruk@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=poeschel@lemonage.de \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=sameo@linux.intel.com \
--cc=tony@atomide.com \
/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).