From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "edmund.raile" <edmund.raile@proton.me>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux1394-devel@lists.sourceforge.net"
<linux1394-devel@lists.sourceforge.net>
Subject: Re: [GIT PULL] firewire updates for v6.17 kernel
Date: Mon, 11 Aug 2025 22:33:02 +0900 [thread overview]
Message-ID: <20250811133302.GB267817@workstation.local> (raw)
In-Reply-To: <pTURxXSK4yF5-FlMBbpWLMW5JUC2s1BvSYdYGKBAgEOpI9z4RhnQsLrrRj7E2Iu02sOznG5ysKRVpXR4ZWFp-CSeSebIP1YGQl7gbFLGeEo=@proton.me>
Hi Edmund,
On Fri, Aug 08, 2025 at 01:50:44PM +0000, edmund.raile wrote:
> Dear Mr. Sakamoto,
> thank you for including me in the pull request, I am honored!
>
> I tested the combination of this pull request and your fix patches [1]
> on arch 6.16.0-1-mainline (based on "Linux 6.16" 038d61fd6422)
> with TI XIO2213B and RME FireFace 800.
>
> [1] https://lore.kernel.org/lkml/20250728015125.17825-1-o-takashi@sakamocchi.jp/
>
> So far audio playback seems perfectly stable:
> days with varying CPU load, compiles, even mprime.
> Suspend also seems fine, even without first powering down / disconnecting
> the FireFace.
> Direct ALSA streaming or pipewire, no issues so far.
>
> Tested-by: Edmund Raile (edmund.raile@proton.me)
>
> Thank you for keeping FireWire alive and even developing it!
Thanks for your test, however it is my previous proposal. The latest one
is "[PATCH v2 0/4] firewire: core: call address handlers outside RCU
read-side critical section"[1]. The difference between two proposals is
just to use kalloc helpers instead of XArray for FCP handlers allocation,
thus not effects to your device.
Anyway, thanks.
[1] https://lore.kernel.org/lkml/20250803122015.236493-1-o-takashi@sakamocchi.jp/
Regards
Takashi Sakamoto
prev parent reply other threads:[~2025-08-11 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-02 5:49 Takashi Sakamoto
2025-08-02 17:03 ` pr-tracker-bot
2025-08-08 13:50 ` edmund.raile
2025-08-11 13:33 ` 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=20250811133302.GB267817@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=edmund.raile@proton.me \
--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®