From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: stefanr@s5r6.in-berlin.de, linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/3] firewire: use single object for user space listeners to dispatch request to IEC 61883-1 FCP region
Date: Wed, 25 Jan 2023 21:07:55 +0900 [thread overview]
Message-ID: <Y9Ebm7Yw9XT06Hx6@workstation> (raw)
In-Reply-To: <873581r76s.wl-tiwai@suse.de>
Hi,
On Mon, Jan 23, 2023 at 09:22:51AM +0100, Takashi Iwai wrote:
> On Fri, 20 Jan 2023 10:03:41 +0100,
> Takashi Sakamoto wrote:
> >
> > Hi,
> >
> > This patch solves long standing issue mentioned by code comment[1] and a
> > commit 281e20323ab7 ("firewire: core: fix use-after-free regression in FCP
> > handler")[2]. This patchset is based on the kernel tree to which another
> > fix is applied[3].
> >
> > To Iwai-san, I would like to ask you picking them to your local
> > tree, then send them to mainline tree as well as sound patches when
> > the merge window is open for v6.3 kernel, unless any question and
> > objection is posted. (Additionally, I have prepared the other patchset for
> > the subsystem.)
>
> As those are spontaneous small fixes, now I merged all three patches
> on topic/firewire branch (on top of the for-linus including your
> previous FireWire core fix), merged back to for-next branch for 6.3.
Thanks for your applying.
> But, I have no will to keep doing this in a long term. I suppose the
> best would be that you'd step up as a maintainer for FireWire
> stack...
Indeed. The next patchset is beyond your courtesy. I posted it to LKML
with my concern. I'm pleased if you follow to it.
* https://lore.kernel.org/lkml/20230125120301.51585-1-o-takashi@sakamocchi.jp/
> thanks,
>
> Takashi
Thanks
Takashi Sakamoto
prev parent reply other threads:[~2023-01-25 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 9:03 [PATCH 0/3] firewire: use single object for user space listeners to dispatch request to IEC 61883-1 FCP region Takashi Sakamoto
2023-01-20 9:03 ` [PATCH 1/3] firewire: core: use kref structure to maintain lifetime of data for fw_request structure Takashi Sakamoto
2023-01-20 9:03 ` [PATCH 2/3] firewire: cdev: obsolete NULL check to detect IEC 61883-1 FCP region Takashi Sakamoto
2023-01-20 9:03 ` [PATCH 3/3] firewire: cdev: use single object to dispatch event for request to " Takashi Sakamoto
2023-01-23 8:22 ` [PATCH 0/3] firewire: use single object for user space listeners to dispatch " Takashi Iwai
2023-01-25 12:07 ` 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=Y9Ebm7Yw9XT06Hx6@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
--cc=tiwai@suse.de \
/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