From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/17] firewire: core/ohci: use guard macro for any type of lock primitives
Date: Tue, 6 Aug 2024 09:06:26 +0900 [thread overview]
Message-ID: <20240806000626.GA264514@workstation.local> (raw)
In-Reply-To: <20240805085408.251763-1-o-takashi@sakamocchi.jp>
On Mon, Aug 05, 2024 at 05:53:51PM +0900, Takashi Sakamoto wrote:
> Hi,
>
> This patchset is a revised version of the previous one.
>
> https://lore.kernel.org/lkml/20240804130225.243496-1-o-takashi@sakamocchi.jp/
>
> The guard macro was firstly introduced in v6.5 kernel, and already
> available for spin_lock, mutex, RCU, and R/W semaphore. It is useful to
> ensure releasing lock in block.
>
> This patchset includes changes to replace lock/release codes with the guard
> macro.
>
> * Changes in v2:
> * use scoped_guard() instead of guard() just after label so that
> statements are expanded there instead of declarations.
>
> Takashi Sakamoto (17):
> firewire: core: use guard macro to maintain static packet data for phy
> configuration
> firewire: core: use guard macro to maintain the list of card
> firewire: core: use guard macro to maintain the list of cdev clients
> firewire: ohci: use guard macro to serialize accesses to phy registers
> firewire: core: use guard macro to maintain RCU scope for transaction
> address handler
> firewire: core: use guard macro to access to IDR for fw_device
> firewire: core: use guard macro to maintain the list of address
> handler for transaction
> firewire: core: use guard macro to disable local IRQ
> firewire: core: use guard macro to maintain list of events for
> userspace clients
> firewire: core: use guard macro to maintain IDR of isochronous
> resources for userspace clients
> firewire: core: use guard macro to maintain isochronous context for
> userspace client
> firewire: core: use guard macro to maintain list of receivers for phy
> configuration packets
> firewire: core: use guard macro to maintain list of asynchronous
> transaction
> firewire: core: use guard macro to maintain properties of fw_card
> firewire: ohci: use guard macro to maintain bus time
> firewire: ohci: use guard macro to maintain image of configuration ROM
> firewire: ohci: use guard macro to serialize operations for
> isochronous contexts
>
> drivers/firewire/core-card.c | 60 ++---
> drivers/firewire/core-cdev.c | 252 ++++++++----------
> drivers/firewire/core-device.c | 83 +++---
> drivers/firewire/core-iso.c | 5 +-
> drivers/firewire/core-topology.c | 5 +-
> drivers/firewire/core-transaction.c | 146 ++++------
> drivers/firewire/ohci.c | 399 ++++++++++++----------------
> 7 files changed, 403 insertions(+), 547 deletions(-)
Applied to for-next branch.
Regards
Takashi Sakamoto
prev parent reply other threads:[~2024-08-06 0:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 8:53 [PATCH v2 00/17] firewire: core/ohci: use guard macro for any type of lock primitives Takashi Sakamoto
2024-08-05 8:53 ` [PATCH v2 01/17] firewire: core: use guard macro to maintain static packet data for phy configuration Takashi Sakamoto
2024-08-05 8:53 ` [PATCH v2 02/17] firewire: core: use guard macro to maintain the list of card Takashi Sakamoto
2024-08-05 8:53 ` [PATCH v2 03/17] firewire: core: use guard macro to maintain the list of cdev clients Takashi Sakamoto
2024-08-05 8:53 ` [PATCH v2 04/17] firewire: ohci: use guard macro to serialize accesses to phy registers Takashi Sakamoto
2024-08-05 8:53 ` [PATCH v2 05/17] firewire: core: use guard macro to maintain RCU scope for transaction address handler Takashi Sakamoto
2024-08-05 8:53 ` [PATCH v2 06/17] firewire: core: use guard macro to access to IDR for fw_device Takashi Sakamoto
2024-08-05 8:53 ` [PATCH v2 07/17] firewire: core: use guard macro to maintain the list of address handler for transaction Takashi Sakamoto
2024-08-05 8:53 ` [PATCH v2 08/17] firewire: core: use guard macro to disable local IRQ Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 09/17] firewire: core: use guard macro to maintain list of events for userspace clients Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 10/17] firewire: core: use guard macro to maintain IDR of isochronous resources " Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 11/17] firewire: core: use guard macro to maintain isochronous context for userspace client Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 12/17] firewire: core: use guard macro to maintain list of receivers for phy configuration packets Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 13/17] firewire: core: use guard macro to maintain list of asynchronous transaction Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 14/17] firewire: core: use guard macro to maintain properties of fw_card Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 15/17] firewire: ohci: use guard macro to maintain bus time Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 16/17] firewire: ohci: use guard macro to maintain image of configuration ROM Takashi Sakamoto
2024-08-05 8:54 ` [PATCH v2 17/17] firewire: ohci: use guard macro to serialize operations for isochronous contexts Takashi Sakamoto
2024-08-06 0:06 ` Takashi Sakamoto [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=20240806000626.GA264514@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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