From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Petre Rodan <petre.rodan@subdimension.ro>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v2 1/4] dt-bindings: iio: pressure: honeywell,hsc030pa.yaml add spi props
Date: Mon, 29 Jan 2024 09:23:36 +0100 [thread overview]
Message-ID: <1de7829c-8e11-4d48-a28a-a7eacc16c8a3@linaro.org> (raw)
In-Reply-To: <20240127160405.19696-2-petre.rodan@subdimension.ro>
On 27/01/2024 17:03, Petre Rodan wrote:
> Add spi-peripheral-props.yaml requirement needed by the
> spi-max-frequency property.
>
> Signed-off-by: Petre Rodan <petre.rodan@subdimension.ro>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-29 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 16:03 [PATCH v2 0/4] iio: pressure: hsc030pa: cleanup and triggered buffer Petre Rodan
2024-01-27 16:03 ` [PATCH v2 1/4] dt-bindings: iio: pressure: honeywell,hsc030pa.yaml add spi props Petre Rodan
2024-01-29 8:23 ` Krzysztof Kozlowski [this message]
2024-01-27 16:03 ` [PATCH v2 2/4] iio: pressure: hsc030pa cleanup Petre Rodan
2024-01-27 16:57 ` Jonathan Cameron
2024-01-27 16:03 ` [PATCH v2 3/4] iio: pressure: hsc030pa add mandatory delay Petre Rodan
2024-01-27 16:03 ` [PATCH v2 4/4] iio: pressure: hsc030pa add triggered buffer Petre Rodan
2024-01-27 16:59 ` Jonathan Cameron
2024-02-04 13:44 ` Jonathan Cameron
2024-02-04 16:10 ` Jonathan Cameron
2024-02-04 16:03 ` andy.shevchenko
2024-02-05 16:39 ` Petre Rodan
2024-02-10 15:09 ` Jonathan Cameron
2024-02-10 15:12 ` Andy Shevchenko
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=1de7829c-8e11-4d48-a28a-a7eacc16c8a3@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petre.rodan@subdimension.ro \
--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