From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, stefanr@s5r6.in-berlin.de
Cc: tiwai@suse.de, broonie@kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem
Date: Fri, 21 Apr 2023 01:02:33 +0900 [thread overview]
Message-ID: <20230420160233.GB33275@workstation> (raw)
In-Reply-To: <20230306035814.78455-1-o-takashi@sakamocchi.jp>
On Mon, Mar 06, 2023 at 12:58:14PM +0900, Takashi Sakamoto wrote:
> In the last few years, I have reviewed patches for FireWire subsystem and
> requested sound subsystem maintainer to sent them to mainline, since
> FireWire subsystem maintainer has been long absent. This situation is not
> preferable since we have some user of sound hardware in IEEE 1394 bus.
>
> I will stand for the maintainer, and work for FireWire core functions and
> 1394 OHCI driver, as well as sound drivers. This commit replaces the
> corresponding entry.
>
> As you know, IEEE 1394 is enough legacy. I would like to schedule the end
> of my work in the subsystem. My effort will last next 6 years. In 2026, I
> will start strong announcement for users to migrate their work load from
> IEEE 1394 bus (e.g. by purchasing alternative devices in USB and hardening
> system for them), then in 2029 let me resign the maintainer and close
> Linux 1394 project.
>
> My current work focuses on real time data (sampling data) transmission
> protocol in packet-oriented communication, thus I would provide less help
> to implementations for the other type of protocol; i.e. IPv4/IPv6 over
> IEEE 1394 bus (firewire-net), SCSI transport protocol over IEEE 1394 bus
> (firewire-sbp2) and iSCSI target (sbp-target).
>
> If receiving few objections from developers, I will start my work to send
> fixes for v6.3 prepatch, and PR for future v6.4 or later. I'm pleased if
> getting any help until the end.
>
> Reference: commit b32744751e75 ("firewire: add to MAINTAINERS")
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> ---
> MAINTAINERS | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
The patch is applied to for-next branch for v6.4 kernel:
* https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git/
Thanks
Takashi Sakamoto
prev parent reply other threads:[~2023-04-20 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 3:58 [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem Takashi Sakamoto
2023-03-06 22:17 ` Randy Dunlap
2023-03-09 14:14 ` Takashi Iwai
2023-03-10 20:03 ` Stefan Richter
2023-03-11 8:03 ` Takashi Sakamoto
2023-03-11 9:15 ` Stefan Richter
2023-03-12 7:07 ` Takashi Sakamoto
2023-04-09 23:56 ` Randy Dunlap
2023-04-17 14:17 ` Takashi Sakamoto
2023-04-20 16:02 ` 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=20230420160233.GB33275@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=rdunlap@infradead.org \
--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