From: <Ariana.Lazar@microchip.com>
To: <conor@kernel.org>
Cc: <dlechner@baylibre.com>, <nuno.sa@analog.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<robh@kernel.org>, <jic23@kernel.org>, <andy@kernel.org>,
<krzk+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<conor+dt@kernel.org>
Subject: Re: [PATCH 2/3] dt-bindings: iio: dac: add support for MCP48FEB02 SPI
Date: Fri, 24 Jul 2026 12:30:31 +0000 [thread overview]
Message-ID: <7e121a7afaaa5aa72e39a4a70de2b0edff796def.camel@microchip.com> (raw)
In-Reply-To: <20260723-festive-genetics-3645c8e0b318@spud>
Hi Conor,
> This is actually a v2, right? This was submitted before using a bit
> of a
> different approach IIRC?
This is the first version combining both the refactoring and the SPI
support into a single series. Originally I have sent the refactoring
patches separately and in order to avoid confusion (cannot do a diff
with old patches) and to be tracked easily I have decided to make this
series as version 1.
If you think it is a good idea to mark it as version 2, I can resend
the series as version 2 and point to the old patches as version 1.
Best regards,
Ariana
next prev parent reply other threads:[~2026-07-24 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260723-mcp47feb02_refactor-v1-0-ee59e63672bc@microchip.com>
[not found] ` <20260723-mcp47feb02_refactor-v1-2-ee59e63672bc@microchip.com>
2026-07-23 16:38 ` [PATCH 2/3] dt-bindings: iio: dac: add support for MCP48FEB02 SPI Conor Dooley
2026-07-24 12:30 ` Ariana.Lazar [this message]
2026-07-24 12:44 ` Conor Dooley
[not found] ` <20260723-mcp47feb02_refactor-v1-3-ee59e63672bc@microchip.com>
2026-07-23 21:02 ` [PATCH 3/3] iio: dac: add support for Microchip MCP48FEB02 Joshua Crofts
[not found] ` <20260723-mcp47feb02_refactor-v1-1-ee59e63672bc@microchip.com>
2026-07-23 21:18 ` [PATCH 1/3] iio: dac: mcp47feb02: refactor MCP47FEB02 I2C driver into two modules Joshua Crofts
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=7e121a7afaaa5aa72e39a4a70de2b0edff796def.camel@microchip.com \
--to=ariana.lazar@microchip.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--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