From: Rob Herring <robh@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Sean Nyekjaer <sean@geanix.com>
Subject: Re: [PATCH] dt-bindings: iio: ti,ads8688 yaml conversion
Date: Wed, 15 Jul 2020 15:57:44 -0600 [thread overview]
Message-ID: <20200715215744.GA879805@bogus> (raw)
In-Reply-To: <20200705131720.240574-1-jic23@kernel.org>
On Sun, Jul 05, 2020 at 02:17:20PM +0100, Jonathan Cameron wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> Fairly simple binding. Most of the changes were filling in information
> not previously found in the binding. I dropped the previous explicit
> mention of spi-max-frequency as that is covered by the generic SPI
> binding.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: Sean Nyekjaer <sean@geanix.com>
> ---
>
> Sean, are you fine with being explicitly listed at the maintainer
> of this binding? Previously we didn't have that formally laid
> out in the old txt bindings but it's now a required field.
>
> I'm going to slowly work my way through some of the simpler yaml conversions
> over the next few months. Of course I welcome anyone else taking
> some of these on but for purposes of review, please keep it to only
> a few at a time.
Actually, I'd really prefer a bunch at a time if it is by one person.
Not because I need more to review :P, but then all the mistakes are the
same and can be fixed in one go. I have a script[1] I use that does some
of the boilerplate, but not the hard part (properties). It works best if
you tweak the template with what's common for a set of bindings.
Rob
[1] https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/commit/?h=yaml-bindings-v2
next prev parent reply other threads:[~2020-07-15 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 13:17 [PATCH] dt-bindings: iio: ti,ads8688 yaml conversion Jonathan Cameron
2020-07-06 7:51 ` Sean Nyekjaer
2020-07-15 21:57 ` Rob Herring [this message]
2020-07-18 16:33 ` Jonathan Cameron
2020-07-15 21:58 ` Rob Herring
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=20200715215744.GA879805@bogus \
--to=robh@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=sean@geanix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.