From: <Ariana.Lazar@microchip.com>
To: <jic23@kernel.org>
Cc: <linux-iio@vger.kernel.org>, <nuno.sa@analog.com>,
<dlechner@baylibre.com>, <linux-kernel@vger.kernel.org>,
<andy@kernel.org>
Subject: Re: [PATCH v2] iio: dac: mcp47feb02: refactor MCP47FEB02 I2C driver into two modules
Date: Wed, 3 Jun 2026 14:52:41 +0000 [thread overview]
Message-ID: <09f59aacb059342e2698b370af4536d4e7a90938.camel@microchip.com> (raw)
In-Reply-To: <20260528125140.16a8f173@jic23-huawei>
Hi Jonathan,
Thank you for the review.
> I don't mind reviewing this on it's own but won't merge it until
> we have a reason (i.e. that SPI part)
>
In the first version of this patch series the SPI file was included
too, but it was recommended not to for better clarity:
https://lore.kernel.org/all/20260419171658.2dbb9884@jic23-huawei/
My understanding was to submit a driver refactoring (splitting the
driver into core and I2C modules) and submit later another patch to add
the SPI part (the SPI module and modified dt binding). Please tell me
if this is alright or I should do it differently.
>
>
> All of these belong in separate patches from the fundamental code
> move. Probably before it given they seem like a good idea anyway..
>
After mcp47feb02 I2C driver was accepted in upstream I've submitted a
new patch series for mcp48feb02 SPI driver. Changes I did among the
refactor were from the review for that driver:
https://lore.kernel.org/all/aY3m5V05FOH5sut6@smile.fi.intel.com/
I will remove the reference mismatch part, which is a fix for
mcp47feb02, and I will submit it in v3 for the series:
https://lore.kernel.org/all/20260414-mcp47feb02-fix4-v1-1-9d71badfd25e@microchip.com/
in order to add the fixes from later reviews (even if those patches
will not be continued).
Best regards,
Ariana
next prev parent reply other threads:[~2026-06-03 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 14:50 Ariana Lazar
2026-05-28 11:51 ` Jonathan Cameron
2026-06-03 14:52 ` Ariana.Lazar [this message]
2026-06-04 10:51 ` 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=09f59aacb059342e2698b370af4536d4e7a90938.camel@microchip.com \
--to=ariana.lazar@microchip.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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
all inboxes | Powered by JetHome®