From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: gomba007@gmail.com, Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: trivial-devices: Document SEN0322
Date: Mon, 5 May 2025 17:53:40 +0100 [thread overview]
Message-ID: <20250505175340.00b6861b@jic23-huawei> (raw)
In-Reply-To: <3d42e605-2526-4eb1-b222-6552629333ef@kernel.org>
On Mon, 5 May 2025 10:16:06 +0200
Krzysztof Kozlowski <krzk@kernel.org> wrote:
> On 05/05/2025 09:52, Tóth János via B4 Relay wrote:
> > From: Tóth János <gomba007@gmail.com>
> >
> > Add documentation for the DFRobot SEN0322 oxygen sensor.
> >
> > Signed-off-by: Tóth János <gomba007@gmail.com>
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Best regards,
> Krzysztof
>
Hmm. This is fine I guess, but I'm never sure how pretty much anything
justifies being in trivial-devices.yaml given they should all be full bindings
and almost anything requires a power supply :)
Maybe we should let there be a few standard supplies for the devices
in there in the same way a single interrupt is allowed?
J
next prev parent reply other threads:[~2025-05-05 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 7:52 [PATCH v2 0/2] Add support for the DFRobot SEN0322 oxygen sensor Tóth János via B4 Relay
2025-05-05 7:52 ` [PATCH v2 1/2] dt-bindings: trivial-devices: Document SEN0322 Tóth János via B4 Relay
2025-05-05 8:16 ` Krzysztof Kozlowski
2025-05-05 16:53 ` Jonathan Cameron [this message]
2025-05-05 7:52 ` [PATCH v2 2/2] iio: chemical: Add driver for SEN0322 Tóth János via B4 Relay
2025-05-05 17:47 ` Jonathan Cameron
2025-05-06 7:52 ` Tóth János
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=20250505175340.00b6861b@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gomba007@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@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