mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Nithishvelan M <mnithishvelan@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Nuno Sa <nuno.sa@analog.com>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: iio: impedance-analyzer: ad5933: use guard(mutex) in ad5933_show()
Date: Mon, 19 Oct 2026 12:53:33 +0300	[thread overview]
Message-ID: <atXoncij2_IrGjZZ@ashevche-desk.local> (raw)
In-Reply-To: <20261018200128.642-1-mnithishvelan@gmail.com>

On Sun, Oct 18, 2026 at 08:01:27PM +0000, Nithishvelan M wrote:
> Use guard(mutex) to automatically manage the state lock in
> ad5933_show(). This simplifies the function by allowing direct returns
> from each switch case, eliminating the mutable return variables and
> manual mutex_unlock() calls.

...

>  	switch ((u32)this_attr->address) {
>  	case AD5933_OUT_RANGE:
> -		len = sysfs_emit(buf, "%u\n",
> -				 st->range_avail[(st->ctrl_hb >> 1) & 0x3]);
> -		break;
> +		return sysfs_emit(buf, "%u\n",
> +				  st->range_avail[(st->ctrl_hb >> 1) & 0x3]);

Keep it on a single (not so long) line.

		return sysfs_emit(buf, "%u\n", st->range_avail[(st->ctrl_hb >> 1) & 0x3]);

Most likely Sashiko might warn of use ctrl_hb variable as an index without
checking. So it might make sense to be prepared for that by adding a local
variable:

		unsigned int ridx = (st->ctrl_hb >> 1) & 0x03;

		return sysfs_emit(buf, "%u\n", st->range_avail[ridx]);


>  	case AD5933_OUT_RANGE_AVAIL:
> -		len = sysfs_emit(buf, "%u %u %u %u\n", st->range_avail[0],
> -				 st->range_avail[3], st->range_avail[2],
> -				 st->range_avail[1]);
> -		break;
> +		return sysfs_emit(buf, "%u %u %u %u\n", st->range_avail[0],
> +				  st->range_avail[3], st->range_avail[2],
> +				  st->range_avail[1]);

Split logically

		return sysfs_emit(buf, "%u %u %u %u\n",
				  st->range_avail[0], st->range_avail[3],
				  st->range_avail[2], st->range_avail[1]);

>  	case AD5933_OUT_SETTLING_CYCLES:
> -		len = sysfs_emit(buf, "%d\n", st->settling_cycles);
> -		break;
> +		return sysfs_emit(buf, "%d\n", st->settling_cycles);
>  	case AD5933_IN_PGA_GAIN:
> -		len = sysfs_emit(buf, "%s\n",
> -				 (st->ctrl_hb & AD5933_CTRL_PGA_GAIN_1) ?
> -				 "1" : "0.2");
> -		break;
> +		return sysfs_emit(buf, "%s\n",

> +				  (st->ctrl_hb & AD5933_CTRL_PGA_GAIN_1) ?
> +				  "1" : "0.2");

A single line

				  (st->ctrl_hb & AD5933_CTRL_PGA_GAIN_1) ?  "1" : "0.2");

and, IIRC the operator precedences, the parentheses can be dropped.

>  	case AD5933_IN_PGA_GAIN_AVAIL:
> -		len = sysfs_emit(buf, "1 0.2\n");
> -		break;
> +		return sysfs_emit(buf, "1 0.2\n");
>  	case AD5933_FREQ_POINTS:
> -		len = sysfs_emit(buf, "%d\n", st->freq_points);
> -		break;
> +		return sysfs_emit(buf, "%d\n", st->freq_points);
>  	default:
> -		ret = -EINVAL;
> +		return -EINVAL;
>  	}

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2026-10-19  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 20:01 Nithishvelan M
2026-10-19  9:53 ` Andy Shevchenko [this message]

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=atXoncij2_IrGjZZ@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mnithishvelan@gmail.com \
    --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®