From: Dmitry Osipenko <digetx@gmail.com>
To: David Heidelberg <david@ixit.cz>, linux-iio@vger.kernel.org
Cc: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Daniel Baluta" <daniel.baluta@nxp.com>,
"Jonathan Cameron" <jic23@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>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/7] dt-bindings: iio: light: add support for Dyna-Image AL3320A
Date: Sat, 1 Feb 2020 21:59:22 +0300 [thread overview]
Message-ID: <2c026269-079e-01fb-b469-87c6d4f2983e@gmail.com> (raw)
In-Reply-To: <20200201180024.328700-3-david@ixit.cz>
01.02.2020 21:00, David Heidelberg пишет:
> Subject: [PATCH v3 2/7] dt-bindings: iio: light: add support for Dyna-Image
> AL3010
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
Looks like something went wrong, ^ this shouldn't be in the patch's body.
> The Dyna-Image AL3010 is a 16-bit digital ambient light sensor which
> provides a multiple gain function with linear response over a dynamic
> range 1216/4863/19452/77806.
>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
You should put individual changelog for each patch under the ---, or
just add a cover-letter with global changelog.
> .../devicetree/bindings/iio/light/al3010.yaml | 45 +++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/light/al3010.yaml
...
prev parent reply other threads:[~2020-02-01 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200201180024.328700-1-david@ixit.cz>
2020-02-01 18:00 ` [PATCH v3 1/7] dt-bindings: iio: light: add support for Dyna-Image AL3320A David Heidelberg
2020-02-01 18:00 ` David Heidelberg
2020-02-01 18:59 ` Dmitry Osipenko [this message]
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=2c026269-079e-01fb-b469-87c6d4f2983e@gmail.com \
--to=digetx@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mirq-linux@rere.qmqm.pl \
--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).