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: simplify pending transaction cancellation on card removal
Date: Sun, 18 Oct 2026 22:15:20 +0900	[thread overview]
Message-ID: <20261018131520.GA389835@sakamocchi.jp> (raw)
In-Reply-To: <20261018063056.329226-1-o-takashi@sakamocchi.jp>

On Sun, Oct 18, 2026 at 03:30:53PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> This series simplifies the handling of pending transactions by using
> workqueue when a card is removed. It also improves the checking of
> preconditions for scheduling error callbacks by moving the warning check
> to the scheduling helper and using compiler-based context analysis to
> verify lock state.
> 
> 
> Takashi Sakamoto (3):
>   firewire: core: use workqueue to cancel all pending transactions on
>     card removal
>   firewire: core: check precondition when scheduling error callbacks
>   firewire: core: use context analysis to check lock state when
>     scheduling error callbacks
> 
>  drivers/firewire/core-card.c        |  4 +-
>  drivers/firewire/core-transaction.c | 76 ++++++++++++++---------------
>  2 files changed, 40 insertions(+), 40 deletions(-)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2026-10-18 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18  6:30 Takashi Sakamoto
2026-10-18  6:30 ` [PATCH 1/3] firewire: core: use workqueue to cancel all pending transactions " Takashi Sakamoto
2026-10-18  6:30 ` [PATCH 2/3] firewire: core: check precondition when scheduling error callbacks Takashi Sakamoto
2026-10-18  6:30 ` [PATCH 3/3] firewire: core: use context analysis to check lock state " Takashi Sakamoto
2026-10-18 13:15 ` 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=20261018131520.GA389835@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®