public inbox for linux-kernel@vger.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 0/4] firewire: core: code refactoring for isoc resource management work in cdev layer
Date: Sun, 3 May 2026 20:47:14 +0900	[thread overview]
Message-ID: <20260503114714.GA353219@sakamocchi.jp> (raw)
In-Reply-To: <20260501135823.241940-1-o-takashi@sakamocchi.jp>

On Fri, May 01, 2026 at 10:58:19PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> In the cdev layer of this subsystem, there are two ways to manage
> isochronous resources. My previous work separated the logic for these
> approaches[1]. However, there is still room to improve the current
> implementation, particularly in the code path that maintains
> isochronous resources managed by the kernel, where the current code can
> be simplified.
> 
> This patchset refactors the relevant code accordingly.
> 
> 
> [1] https://lore.kernel.org/lkml/20260429093449.160545-1-o-takashi@sakamocchi.jp/
> 
> Takashi Sakamoto (4):
>   firewire: core: reduce critical section duration in pre-processing of
>     isoc resource management in cdev
>   firewire: core: use switch statement for post-processing of isoc
>     resource management in cdev
>   firewire: core: refactor notification type determination after isoc
>     resource management in cdev
>   firewire: core: move allocation/reallocation paths into specific branch
>     after isoc resource management in cdev
> 
>  drivers/firewire/core-cdev.c | 115 +++++++++++++++++++----------------
>  1 file changed, 64 insertions(+), 51 deletions(-)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2026-05-03 11:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 13:58 [PATCH 0/4] firewire: core: code refactoring for isoc resource management work in cdev layer Takashi Sakamoto
2026-05-01 13:58 ` [PATCH 1/4] firewire: core: reduce critical section duration in pre-processing of isoc resource management in cdev Takashi Sakamoto
2026-05-01 13:58 ` [PATCH 2/4] firewire: core: use switch statement for post-processing " Takashi Sakamoto
2026-05-01 13:58 ` [PATCH 3/4] firewire: core: refactor notification type determination after " Takashi Sakamoto
2026-05-01 13:58 ` [PATCH 4/4] firewire: core: move allocation/reallocation paths into specific branch " Takashi Sakamoto
2026-05-03 11:47 ` 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=20260503114714.GA353219@sakamocchi.jp \
    --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