From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>,
maddy@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com, christophe.leroy@csgroup.eu,
mpe@ellerman.id.au, peterz@infradead.org, ajd@linux.ibm.com,
mahesh@linux.ibm.com, hbathini@linux.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] powerpc: use lock guards for mutex Set 1
Date: Mon, 5 May 2025 19:52:44 +0530 [thread overview]
Message-ID: <898a1a58-ae8d-4210-9f4e-9e97c9e0cb82@linux.ibm.com> (raw)
In-Reply-To: <20250505075333.184463-1-sshegde@linux.ibm.com>
On 05/05/25 1:23 pm, Shrikanth Hegde wrote:
> This is an effort to make the code simpler by making use of lock
> guards which were introduced in [1], which works by using __cleanup
> attributes. More details in v1 cover letter
>
> v2->v3:
> - Collects tags (Andrew Donnellan & Srikar Dronamraju)
> - Address comments from Srikar Dronamraju
>
> v1->v2:
> - Fix changelog of powernv (Andrew Donnellan)
> - use scoped_guard in couple of places to avoid holding mutex
> un-necessarily (Peter Zijlstra)
>
> [1]: https://lkml.kernel.org/r/20230612093537.614161713%40infradead.org
> v1: https://lore.kernel.org/all/20250314054544.1998928-1-sshegde@linux.ibm.com/#t
> v2: https://lore.kernel.org/all/20250314114502.2083434-1-sshegde@linux.ibm.com/
>
> Shrikanth Hegde (6):
> powerpc: eeh: use lock guard for mutex
> powerpc: rtas: use lock guard for mutex
> powerpc: fadump: use lock guard for mutex
> powerpc: book3s: vas: use lock guard for mutex
> powerpc: powernv: ocxl: use lock guard for mutex
> powerpc: sysdev: use lock guard for mutex
>
> arch/powerpc/kernel/eeh.c | 20 +++----
> arch/powerpc/kernel/fadump.c | 11 ++--
> arch/powerpc/kernel/rtas_flash.c | 64 +++++++--------------
> arch/powerpc/platforms/book3s/vas-api.c | 32 +++++------
> arch/powerpc/platforms/powernv/ocxl.c | 12 +---
> arch/powerpc/sysdev/fsl_mpic_timer_wakeup.c | 14 +----
> 6 files changed, 50 insertions(+), 103 deletions(-)
>
Tested this patch-set by applying on top of powerpc repo, with HEAD:
b4432656b36e5cc1d50a1f2dc15357543add530e, and Build and boot test is
successful.
Also FADUMP and DLPAR operations are successful. Hence, for the series,
Tested-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Regards,
Venkat.
prev parent reply other threads:[~2025-05-05 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 7:53 [PATCH v3 0/6] powerpc: use lock guards for mutex Set 1 Shrikanth Hegde
2025-05-05 7:53 ` [PATCH v3 1/6] powerpc: eeh: use lock guard for mutex Shrikanth Hegde
2025-05-05 7:53 ` [PATCH v3 2/6] powerpc: rtas: " Shrikanth Hegde
2025-05-05 7:53 ` [PATCH v3 3/6] powerpc: fadump: " Shrikanth Hegde
2025-05-08 5:53 ` Sourabh Jain
2025-05-09 13:02 ` Shrikanth Hegde
2025-05-05 7:53 ` [PATCH v3 4/6] powerpc: book3s: vas: " Shrikanth Hegde
2025-05-05 7:53 ` [PATCH v3 5/6] powerpc: powernv: ocxl: " Shrikanth Hegde
2025-05-05 7:53 ` [PATCH v3 6/6] powerpc: sysdev: " Shrikanth Hegde
2025-05-05 9:45 ` [PATCH v3 0/6] powerpc: use lock guards for mutex Set 1 Shrikanth Hegde
2025-05-05 14:22 ` Venkat Rao Bagalkote [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=898a1a58-ae8d-4210-9f4e-9e97c9e0cb82@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=hbathini@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.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