All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] firewire: code refactoring mainly for bm_work
Date: Tue, 9 Sep 2025 06:08:51 +0900	[thread overview]
Message-ID: <20250908210851.GA586497@workstation.local> (raw)
In-Reply-To: <20250908012108.514698-1-o-takashi@sakamocchi.jp>

On Mon, Sep 08, 2025 at 10:20:57AM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> The core function in this subsystem have bm_work work item. The
> corresponding function has many lines with comments. It is a sign
> that it is time to be refactored, in my experience.
> 
> This series includes the first take for the purpose, as well as the
> other code improvements of 1394 OHCI PCI driver and the other core
> functions.
> 
> Takashi Sakamoto (11):
>   firewire: ohci: use kcalloc() variant for array allocation
>   firewire: core: utilize cleanup function to release workqueue in error
>     path
>   firewire: ohci: use return value from fw_node_get()
>   firewire: core: add helper functions to access to fw_device data in
>     fw_node structure
>   firewire: core: use cleanup function in bm_work
>   firewire: ohci: localize transaction data and rcode per condition
>     branch
>   firewire: core: code refactoring to evaluate transaction result to
>     CSR_BUS_MANAGER_ID
>   firewire: core: refer fw_card member to initiate bus reset under
>     acquiring lock
>   firewire: core: code refactoring to detect both IEEE 1394:1995 IRM and
>     Canon MV5i
>   firewire: core: code refactoring to investigate root node for bus
>     manager
>   firewire: core: code refactoring whether root node is cycle master
>     capable
> 
>  drivers/firewire/core-card.c   | 239 +++++++++++++++++----------------
>  drivers/firewire/core-device.c |  18 +--
>  drivers/firewire/core.h        |  14 +-
>  drivers/firewire/ohci.c        |   7 +-
>  4 files changed, 143 insertions(+), 135 deletions(-)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2025-09-08 21:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08  1:20 [PATCH 00/11] firewire: code refactoring mainly for bm_work Takashi Sakamoto
2025-09-08  1:20 ` [PATCH 01/11] firewire: ohci: use kcalloc() variant for array allocation Takashi Sakamoto
2025-09-08  1:20 ` [PATCH 02/11] firewire: core: utilize cleanup function to release workqueue in error path Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 03/11] firewire: ohci: use return value from fw_node_get() Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 04/11] firewire: core: add helper functions to access to fw_device data in fw_node structure Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 05/11] firewire: core: use cleanup function in bm_work Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 06/11] firewire: ohci: localize transaction data and rcode per condition branch Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 07/11] firewire: core: code refactoring to evaluate transaction result to CSR_BUS_MANAGER_ID Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 08/11] firewire: core: refer fw_card member to initiate bus reset under acquiring lock Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 09/11] firewire: core: code refactoring to detect both IEEE 1394:1995 IRM and Canon MV5i Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 10/11] firewire: core: code refactoring to investigate root node for bus manager Takashi Sakamoto
2025-09-08  1:21 ` [PATCH 11/11] firewire: core: code refactoring whether root node is cycle master capable Takashi Sakamoto
2025-09-08 21:08 ` 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=20250908210851.GA586497@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.