From: Srikar Dronamraju <srikar@linux.ibm.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: maddy@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
npiggin@gmail.com, christophe.leroy@csgroup.eu,
mpe@ellerman.id.au, peterz@infradead.org, fbarrat@linux.ibm.com,
ajd@linux.ibm.com, mahesh@linux.ibm.com, oohall@gmail.com,
hbathini@linux.ibm.com, dhowells@redhat.com, haren@linux.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] powerpc: use lock guards for mutex Set 1
Date: Wed, 30 Apr 2025 18:59:17 +0530 [thread overview]
Message-ID: <aBIlrYRE8TvWAKI_@linux.ibm.com> (raw)
In-Reply-To: <20250314114502.2083434-1-sshegde@linux.ibm.com>
* Shrikanth Hegde <sshegde@linux.ibm.com> [2025-03-14 17:14:56]:
> 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
>
> This series aims mainly at simplifying code around mutex with goto
> statements. If it makes sense, there are more code simplification which
> can done for preempt, rcu, spinlock as well. Even for mutex, there is
> more which could be done. Even there are usecases for kfree which could
> use the new __free infra.
>
> Please review. Code is compile/boot tested except for powernv.
> Have kept the patches separate for easier bisect. Let me if they should
> be combined into one. Commit message is same for all.
>
> [1]: https://lkml.kernel.org/r/20230612093537.614161713%40infradead.org
> v1: https://lore.kernel.org/all/20250314054544.1998928-1-sshegde@linux.ibm.com/#t
>
> v1->v2:
> - Fix changelog of powernv (Andrew Donnellan)
> - use scoped_guard in couple of places to avoid holding mutex
> un-necessarily (Peter Zijlstra)
>
> 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
>
For all the patches in this series
Reviewed-by: Srikar Dronamraju <srikar@linux.ibm.com>
--
Thanks and Regards
Srikar Dronamraju
prev parent reply other threads:[~2025-04-30 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 11:44 [PATCH v2 0/6] powerpc: use lock guards for mutex Set 1 Shrikanth Hegde
2025-03-14 11:44 ` [PATCH v2 1/6] powerpc: eeh: use lock guard for mutex Shrikanth Hegde
2025-03-14 11:44 ` [PATCH v2 2/6] powerpc: rtas: " Shrikanth Hegde
2025-03-14 11:44 ` [PATCH v2 3/6] powerpc: fadump: " Shrikanth Hegde
2025-03-14 11:45 ` [PATCH v2 4/6] powerpc: book3s: vas: " Shrikanth Hegde
2025-03-14 11:45 ` [PATCH v2 5/6] powerpc: powernv: ocxl: " Shrikanth Hegde
2025-03-19 4:00 ` Andrew Donnellan
2025-03-14 11:45 ` [PATCH v2 6/6] powerpc: sysdev: " Shrikanth Hegde
2025-04-30 13:10 ` Srikar Dronamraju
2025-05-05 4:02 ` Shrikanth Hegde
2025-04-30 13:29 ` Srikar Dronamraju [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=aBIlrYRE8TvWAKI_@linux.ibm.com \
--to=srikar@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dhowells@redhat.com \
--cc=fbarrat@linux.ibm.com \
--cc=haren@linux.ibm.com \
--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=oohall@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;
as well as URLs for NNTP newsgroup(s).