All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, stefanr@s5r6.in-berlin.de,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] firewire: use single object for user space listeners to dispatch request to IEC 61883-1 FCP region
Date: Mon, 23 Jan 2023 09:22:51 +0100	[thread overview]
Message-ID: <873581r76s.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230120090344.296451-1-o-takashi@sakamocchi.jp>

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.

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...


thanks,

Takashi

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
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: Mon, 23 Jan 2023 09:22:51 +0100	[thread overview]
Message-ID: <873581r76s.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230120090344.296451-1-o-takashi@sakamocchi.jp>

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.

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...


thanks,

Takashi

  parent reply	other threads:[~2023-01-23  8:23 UTC|newest]

Thread overview: 12+ 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 ` 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   ` 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   ` 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-20  9:03   ` Takashi Sakamoto
2023-01-23  8:22 ` Takashi Iwai [this message]
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
2023-01-25 12:07     ` Takashi Sakamoto

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=873581r76s.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=o-takashi@sakamocchi.jp \
    --cc=stefanr@s5r6.in-berlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.