linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Vaussard <florian.vaussard@heig-vd.ch>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Florian Vaussard <florian.vaussard@gmail.com>,
	<devicetree@vger.kernel.org>, Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Martin Kepplinger <martink@posteo.de>,
	<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Vaussard Florian <florian.vaussard@heig-vd.ch>
Subject: Re: [PATCH v3 1/2] iio: adc: max1363: Add device tree binding documentation
Date: Mon, 4 Jul 2016 08:56:05 +0200	[thread overview]
Message-ID: <577A0885.10209@heig-vd.ch> (raw)
In-Reply-To: <57424d5d-2b28-2ea1-153c-6282899492a9@kernel.org>

Hi Jonathan,

On 07/03/2016 12:41 PM, Jonathan Cameron wrote:
> On 30/06/16 08:43, Florian Vaussard wrote:
>> Add the device tree documentation for all the supported parts. Mandatory
>> binding is the compatible string and the slave I2C address.
>>
>> Optional properties can be used to specify the Vcc / Vref regulators, as
>> well as the IRQ line if available.
>>
>> Acked-by: Rob Herring <robh@kernel.org>
>> Signed-off-by: Florian Vaussard <florian.vaussard@heig-vd.ch>
> Really small point, but typically author sign off goes first then acks etc
> that are gained at any intermediate states, then the sign off of whoever takes
> the patch and applies it (here, that's me).  So it kind of communicates some
> idea of when in the process various tags were obtained.  It's not a rule
> set in stone though so I'll be lazy and leave this as it is.
> 

Agree, I will try to stick to this in the future. Looking at some previous
patches, I see that I used both styles without noticing.

> Anyhow, great and applied to the togreg branch of iio.git initially pushed
> out as testing for the autobuilders to poke it (or not in the case of this
> docume
> 

Great. Do you plan to send them for the next merge window, or will you wait for
the 4.9 cycle?

Best,
Florian

  reply	other threads:[~2016-07-04  6:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30  7:43 [PATCH v3 0/2] iio: adc: max1363: Add device tree support Florian Vaussard
2016-06-30  7:43 ` [PATCH v3 1/2] iio: adc: max1363: Add device tree binding documentation Florian Vaussard
2016-07-03 10:41   ` Jonathan Cameron
2016-07-04  6:56     ` Florian Vaussard [this message]
2016-07-05 20:42       ` Jonathan Cameron
2016-06-30  7:43 ` [PATCH v3 2/2] iio: adc: max1363: Add device tree binding Florian Vaussard
2016-07-03 10:41   ` Jonathan Cameron

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=577A0885.10209@heig-vd.ch \
    --to=florian.vaussard@heig-vd.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.vaussard@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martink@posteo.de \
    --cc=pawel.moll@arm.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@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).