public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Maxwell Doose <m32285159@gmail.com>
Cc: rafael@kernel.org, lenb@kernel.org, andy@kernel.org,
	westeri@kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] ACPI: pmic: Replace mutex_lock/unlock() with guard()/scoped_guard()
Date: Wed, 29 Apr 2026 12:55:05 +0300	[thread overview]
Message-ID: <afHVeVavSJ2NZ480@ashevche-desk.local> (raw)
In-Reply-To: <20260429012432.120830-1-m32285159@gmail.com>

On Tue, Apr 28, 2026 at 08:24:32PM -0500, Maxwell Doose wrote:

...

>  v4:
>  - Added else keyword to if statement in
>    intel_soc_pmic_exec_mipi_pmic_seq_element() per Andy's request.

Nope, sorry if I was not clear. The idea is to drop 'else'.
Also make the patch less invasive.

...

> -			       __func__, i2c_address, reg_address, value, mask);

> +				__func__, i2c_address, reg_address, value, mask);

Still a stray change.

...

It should be

	int ret; // also left untouched, drop that from commit message as well

        if (d->exec_mipi_pmic_seq_element) {
		// the below if-else-if just should be left untouched.
		if (i2c_address == d->pmic_i2c_address) {
			...
		} else {
			...
		}

		return ret;
	}

	if (d->pmic_i2c_address) {
	}

	...warnings...
	return -EOPNOTSUPP;

We may get a second patch for deeper refactoring later on.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-04-29  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  1:24 [PATCH v4] ACPI: pmic: Replace mutex_lock/unlock() with guard()/scoped_guard() Maxwell Doose
2026-04-29  9:55 ` Andy Shevchenko [this message]
2026-04-29 13:14   ` Maxwell Doose
2026-04-29 13:31     ` Andy Shevchenko

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=afHVeVavSJ2NZ480@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m32285159@gmail.com \
    --cc=rafael@kernel.org \
    --cc=westeri@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