Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Erick Karanja <karanja99erick@gmail.com>
Cc: logang@deltatee.com, kurt.schwemmer@microsemi.com,
	bhelgaas@google.com, julia.lawall@inria.fr,
	kelvin.cao@microchip.com, wesley.sheng@microchip.com,
	stephen.bates@microsemi.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: switchtec: Replace manual locks with guard
Date: Thu, 28 Aug 2025 10:40:57 -0500	[thread overview]
Message-ID: <20250828154057.GA945052@bhelgaas> (raw)
In-Reply-To: <20250828093556.810911-1-karanja99erick@gmail.com>

On Thu, Aug 28, 2025 at 12:35:55PM +0300, Erick Karanja wrote:
> Replace lock/unlock pairs with guards to simplify and tidy up the code
> 
> Generated-by: Coccinelle SmPL
> 
> Signed-off-by: Erick Karanja <karanja99erick@gmail.com>

Applied to pci/switchtec for v6.18, thanks, Erick!

> ---
>  drivers/pci/switch/switchtec.c | 25 ++++++++++++-------------
>  1 file changed, 12 insertions(+), 13 deletions(-)
> 
> diff --git a/drivers/pci/switch/switchtec.c b/drivers/pci/switch/switchtec.c
> index b14dfab04d84..5ff84fb8fb0f 100644
> --- a/drivers/pci/switch/switchtec.c
> +++ b/drivers/pci/switch/switchtec.c
> @@ -269,10 +269,9 @@ static void mrpc_event_work(struct work_struct *work)
>  
>  	dev_dbg(&stdev->dev, "%s\n", __func__);
>  
> -	mutex_lock(&stdev->mrpc_mutex);
> +	guard(mutex)(&stdev->mrpc_mutex);
>  	cancel_delayed_work(&stdev->mrpc_timeout);
>  	mrpc_complete_cmd(stdev);
> -	mutex_unlock(&stdev->mrpc_mutex);
>  }
>  
>  static void mrpc_error_complete_cmd(struct switchtec_dev *stdev)
> @@ -1322,18 +1321,18 @@ static void stdev_kill(struct switchtec_dev *stdev)
>  	cancel_delayed_work_sync(&stdev->mrpc_timeout);
>  
>  	/* Mark the hardware as unavailable and complete all completions */
> -	mutex_lock(&stdev->mrpc_mutex);
> -	stdev->alive = false;
> -
> -	/* Wake up and kill any users waiting on an MRPC request */
> -	list_for_each_entry_safe(stuser, tmpuser, &stdev->mrpc_queue, list) {
> -		stuser->cmd_done = true;
> -		wake_up_interruptible(&stuser->cmd_comp);
> -		list_del_init(&stuser->list);
> -		stuser_put(stuser);
> -	}
> +	scoped_guard (mutex, &stdev->mrpc_mutex) {
> +		stdev->alive = false;
> +
> +		/* Wake up and kill any users waiting on an MRPC request */
> +		list_for_each_entry_safe(stuser, tmpuser, &stdev->mrpc_queue, list) {
> +			stuser->cmd_done = true;
> +			wake_up_interruptible(&stuser->cmd_comp);
> +			list_del_init(&stuser->list);
> +			stuser_put(stuser);
> +		}
>  
> -	mutex_unlock(&stdev->mrpc_mutex);
> +	}
>  
>  	/* Wake up any users waiting on event_wq */
>  	wake_up_interruptible(&stdev->event_wq);
> -- 
> 2.43.0
> 

      parent reply	other threads:[~2025-08-28 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28  9:35 [PATCH] PCI: switchtec: Replace manual locks with guard Erick Karanja
2025-08-28 15:30 ` Logan Gunthorpe
2025-08-28 15:40 ` Bjorn Helgaas [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=20250828154057.GA945052@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=julia.lawall@inria.fr \
    --cc=karanja99erick@gmail.com \
    --cc=kelvin.cao@microchip.com \
    --cc=kurt.schwemmer@microsemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=stephen.bates@microsemi.com \
    --cc=wesley.sheng@microchip.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