From: <Marius.Cristea@microchip.com>
To: <jic23@kernel.org>, <lars@metafoo.de>,
<krzysztof.kozlowski@linaro.org>, <robh+dt@kernel.org>
Cc: <conor+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<devicetree@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: iio: adc: adding MCP3564 ADC
Date: Wed, 30 Aug 2023 08:33:12 +0000 [thread overview]
Message-ID: <ac2296410c46aac0166252defdf4dd5082c67ebe.camel@microchip.com> (raw)
In-Reply-To: <ab0d99ca-54b9-2535-a783-967a3b2443bf@linaro.org>
Hi Krzysztof,
On Tue, 2023-08-29 at 19:10 +0200, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On 29/08/2023 17:41, marius.cristea@microchip.com wrote:
> > From: Marius Cristea <marius.cristea@microchip.com>
> >
> > This is the device tree schema for iio driver for
> > Microchip family of 153.6 ksps, Low-Noise 16/24-Bit
> > Delta-Sigma ADCs with an SPI interface (Microchip's
> > MCP3461, MCP3462, MCP3464, MCP3461R, MCP3462R,
> > MCP3464R, MCP3561, MCP3562, MCP3564, MCP3561R,
> > MCP3562R and MCP3564R analog to digital converters).
> >
> > Signed-off-by: Marius Cristea <marius.cristea@microchip.com>
> > ---
> > .../bindings/iio/adc/microchip,mcp3564.yaml | 205
> > ++++++++++++++++++
>
> What changed? Cover letter says nothing about binding, so this patch
> must say. Especially that you decided to ignore review.
>
My bad. I was bad handling the resubmition of the patch. I was not
"aware" that I need to keep the "reviewed-by" for the following
patches.
This patch didn't change anything to the "microchip,mcp3564.yaml" file.
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-08-30 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:41 [PATCH v5 0/2] Adding support for Microchip MCP3564 ADC family marius.cristea
2023-08-29 15:41 ` [PATCH v5 1/2] dt-bindings: iio: adc: adding MCP3564 ADC marius.cristea
2023-08-29 15:45 ` Conor Dooley
2023-08-29 16:01 ` Marius.Cristea
2023-08-29 16:18 ` Conor Dooley
2023-08-29 17:10 ` Krzysztof Kozlowski
2023-08-30 8:33 ` Marius.Cristea [this message]
2023-08-29 15:41 ` [PATCH v5 2/2] iio: adc: adding support for " marius.cristea
2023-09-03 11:49 ` Jonathan Cameron
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=ac2296410c46aac0166252defdf4dd5082c67ebe.camel@microchip.com \
--to=marius.cristea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).