linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: ti-adc128s052: Add DT binding documentation
Date: Fri, 26 Dec 2014 11:55:56 +0000	[thread overview]
Message-ID: <549D4CCC.5080503@kernel.org> (raw)
In-Reply-To: <CA+TH9VkQ_yprkV_2PCc57jMoW-=vFr6nXfBAUyy1jLtQetKibw@mail.gmail.com>

On 18/12/14 16:42, Angelo Compagnucci wrote:
> Hi Lars-Peter,
> 
> 2014-12-18 17:18 GMT+01:00 Lars-Peter Clausen <lars@metafoo.de>:
>> On 12/17/2014 06:59 PM, Angelo Compagnucci wrote:
>>>
>>> Adding binding documentation for Texas Instruments' ADC128S052 ADC chip.
>>>
>>> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
>>
>>
>> Looks good to me, but you might want to send this to the devicetree list and
>> the devicetree bindings maintainers.
> 
> Ouch! Resending to the right ml, thank you for your support!
Do keep linux-iio in the loop as well as it'll probably go
through my tree ultimately and I don't read the device-tree list
directly :)  Nature of these patches is that they want to go
to the maintainers, reviewers and lists for both iio and devicetree.

Jonathan
> 
>>
>> [...]
>>>
>>> +Example:
>>> +adc@0 {
>>> +       compatible = "ti,adc128s052";
>>> +       reg = <0>;
>>> +        vref-supply = <&vdd_supply>;
>>
>>
>> strange indention here
>>
>>
>>> +       spi-max-frequency = <1000000>;
>>> +};
>>>
>>
> 
> 
> 


  reply	other threads:[~2014-12-26 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 17:59 [PATCH] iio: ti-adc128s052: Add DT binding documentation Angelo Compagnucci
2014-12-18 16:18 ` Lars-Peter Clausen
2014-12-18 16:42   ` Angelo Compagnucci
2014-12-26 11:55     ` Jonathan Cameron [this message]
2014-12-19 21:53 ` Hartmut Knaack
  -- strict thread matches above, loose matches on Subject: below --
2015-02-16 11:21 Angelo Compagnucci
2015-03-08 12:36 ` Jonathan Cameron
2015-03-08 13:36 Angelo Compagnucci
2015-03-09 11:03 ` Jonathan Cameron
2015-03-08 14:32 Angelo Compagnucci

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=549D4CCC.5080503@kernel.org \
    --to=jic23@kernel.org \
    --cc=angelo.compagnucci@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.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).