From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Artem Shimko <a.shimko.dev@gmail.com>
Cc: andi.shyti@kernel.org, p.zabel@pengutronix.de,
mika.westerberg@linux.intel.com, jsd@semihalf.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] i2c: designware-platdrv: simplify reset control and error handling
Date: Fri, 23 Jan 2026 13:14:13 +0200 [thread overview]
Message-ID: <aXNYBahiKTnVkRfg@smile.fi.intel.com> (raw)
In-Reply-To: <aXNXx4elBVRpWCWf@smile.fi.intel.com>
On Fri, Jan 23, 2026 at 01:13:16PM +0200, Andy Shevchenko wrote:
> On Fri, Jan 23, 2026 at 01:05:34PM +0300, Artem Shimko wrote:
> > Hello maintainers and reviewers,
> >
> > This series refactors the DesignWare platform I2C driver to simplify
> > reset control management and improve error handling:
> >
> > Patch 1 replaces the manual reset control acquisition and deassertion
> > with devm_reset_control_get_optional_exclusive_deasserted(), which
> > combines both operations in a single call and leverages automatic
> > resource management.
> >
> > Patch 2 follows up by refactoring the probe error handling to eliminate
> > goto statements in favor of direct returns with dev_err_probe(), resulting
> > in cleaner and more linear control flow.
> >
> > Both patches maintain functional equivalence while improving code
> > readability and maintainability.
>
> You send a series as _three_ detached emails. Forgot using
>
> git format-patch --thread ...
>
> ?
On top of that, this is marked as v5, where the changelog for all previous
iterations?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-23 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 10:05 [PATCH v5 0/2] i2c: designware-platdrv: simplify reset control and error handling Artem Shimko
2026-01-23 11:13 ` Andy Shevchenko
2026-01-23 11:14 ` Andy Shevchenko [this message]
2026-01-23 11:35 ` Artem Shimko
2026-01-23 14:10 ` Andy Shevchenko
2026-01-23 16:03 ` Artem Shimko
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=aXNYBahiKTnVkRfg@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=a.shimko.dev@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=p.zabel@pengutronix.de \
/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