From: Emil Gedenryd <Emil.Gedenryd@axis.com>
To: "conor@kernel.org" <conor@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dannenberg@ti.com" <dannenberg@ti.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
Kernel <Kernel@axis.com>, "lars@metafoo.de" <lars@metafoo.de>
Subject: Re: [PATCH v2 2/3] dt-bindings: iio: light: opt3001: add compatible for opt3002
Date: Mon, 16 Sep 2024 07:01:44 +0000 [thread overview]
Message-ID: <70d1f90a23e35da3dc12dc4425c4b53c816b2ca9.camel@axis.com> (raw)
In-Reply-To: <20240913-stimulate-swell-3964c45e6e81@spud>
On Fri, 2024-09-13 at 19:07 +0100, Conor Dooley wrote:
> On Fri, Sep 13, 2024 at 11:57:03AM +0200, Emil Gedenryd wrote:
> > OPT3002 is a Light-to-Digital Sensor by TI with support for wide-range
> > spectrum light.
> >
> > Add the compatible string of opt3002.
>
> You should mention what makes the 02 and 01 devices different here, and
> with that done,
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Thanks,
> Conor.
>
>
Thank you, I'll upload a new version as soon as possible.
Best Regards,
Emil
next prev parent reply other threads:[~2024-09-16 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 9:57 [PATCH v2 0/3] iio: light: opt3001: add support for TI's opt3002 light sensor Emil Gedenryd
2024-09-13 9:57 ` [PATCH v2 1/3] iio: light: opt3001: add missing full-scale range value Emil Gedenryd
2024-09-14 16:06 ` Jonathan Cameron
2024-09-16 7:02 ` Emil Gedenryd
2024-09-13 9:57 ` [PATCH v2 2/3] dt-bindings: iio: light: opt3001: add compatible for opt3002 Emil Gedenryd
2024-09-13 18:07 ` Conor Dooley
2024-09-16 7:01 ` Emil Gedenryd [this message]
2024-09-13 9:57 ` [PATCH v2 3/3] iio: light: opt3001: add support for TI's opt3002 light sensor Emil Gedenryd
2024-09-14 16:19 ` Jonathan Cameron
2024-09-16 7:17 ` Emil Gedenryd
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=70d1f90a23e35da3dc12dc4425c4b53c816b2ca9.camel@axis.com \
--to=emil.gedenryd@axis.com \
--cc=Kernel@axis.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=dannenberg@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).