mirror of https://lore.kernel.org/lkml/
 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/3] firewire: core: invoke transaction callbacks in process context
Date: Wed, 23 Sep 2026 09:24:56 +0900	[thread overview]
Message-ID: <20260923002456.GA199647@sakamocchi.jp> (raw)
In-Reply-To: <20260921031931.287429-1-o-takashi@sakamocchi.jp>

On Mon, Sep 21, 2026 at 12:19:28PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> Currently, some error paths invoke the transaction callback in the
> caller's context, while a split transaction timeout invokes it from
> softIRQ context. This makes the execution context of the callback
> inconsistent.
> 
> This series ensures that transaction callbacks are always invoked in
> process context by using a workqueue for the error paths and split
> transaction timeout.
> 
> 
> Takashi Sakamoto (3):
>   firewire: core: refactor invoking transaction callback
>   firewire: core: use workqueue to invoke transaction callback in some
>     error cases
>   firewire: core: update kerneldoc for fw_send_request() and its
>     variants
> 
>  drivers/firewire/core-transaction.c | 91 +++++++++++++++--------------
>  include/linux/firewire.h            | 15 +++--
>  2 files changed, 56 insertions(+), 50 deletions(-)

Applied to for-next.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2026-09-23  0:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  3:19 Takashi Sakamoto
2026-09-21  3:19 ` [PATCH 1/3] firewire: core: refactor invoking transaction callback Takashi Sakamoto
2026-09-21  3:19 ` [PATCH 2/3] firewire: core: use workqueue to invoke transaction callback in some error cases Takashi Sakamoto
2026-09-21  3:19 ` [PATCH 3/3] firewire: core: update kerneldoc for fw_send_request() and its variants Takashi Sakamoto
2026-09-23  0:24 ` 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=20260923002456.GA199647@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

all inboxes | Powered by JetHome®