devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Marius.Cristea@microchip.com>
To: <conor@kernel.org>
Cc: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<lars@metafoo.de>, <linux-kernel@vger.kernel.org>,
	<jic23@kernel.org>, <conor+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <robh+dt@kernel.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: iio: adc: adding MCP3564 ADC
Date: Tue, 29 Aug 2023 16:01:00 +0000	[thread overview]
Message-ID: <8db5512a9ccb0d4f3bb3b0e063c7b43e08e4dadd.camel@microchip.com> (raw)
In-Reply-To: <20230829-legal-superjet-f992cdab2bd3@spud>

Hi Conor

On Tue, 2023-08-29 at 16:45 +0100, Conor Dooley wrote:
> On Tue, Aug 29, 2023 at 06:41:32PM +0300,
> 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>
> 
> Did you intentionally drop my reviewed-by that I gave you on v4?
> 

Sorry that was my mistake. I was not aware that I need to keep the
reviewd-by that you have given me on v4, also on v5.

Thanks,
Marius


  reply	other threads:[~2023-08-29 16:02 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 [this message]
2023-08-29 16:18       ` Conor Dooley
2023-08-29 17:10   ` Krzysztof Kozlowski
2023-08-30  8:33     ` Marius.Cristea
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=8db5512a9ccb0d4f3bb3b0e063c7b43e08e4dadd.camel@microchip.com \
    --to=marius.cristea@microchip.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@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=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).