From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, tiwai@suse.de,
broonie@kernel.org
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem
Date: Sat, 11 Mar 2023 17:03:43 +0900 [thread overview]
Message-ID: <20230311080343.GA378828@workstation> (raw)
In-Reply-To: <20230310210356.561dbe63@kant>
Hi Stefan,
On Fri, Mar 10, 2023 at 09:03:56PM +0100, Stefan Richter wrote:
> On Mar 06 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>
>
> Acked-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
I'm glad to see you again in the list ;)
I really appreciate your long effort for the subsystem. I guess that your
life became swamped recently against your work in the subsystem, while I
feel that soft-landing of the project is still preferable for users.
Below items are in my plan for the subsystem until being closed. I'm
pleased if getting your help in any time.
* 2023, 2024, 2025, 2026
* take over the subsystem maintainer
* set up repositories in `<https://git.kernel.org/>`_
* refresh web site and update information
* take over the administration of communication channels
* adding the list archive of linux1394-devel to
`lore.kernel.org <https://korg.docs.kernel.org/lore.html>`_
* fix issues of subsystem
* modernize 1394 OHCI driver
* Pull requests to Linus
* get help from Linux Foundation to place documents for specification
defined by 1394 Trade Association
* If no problems, upload the documents to the new web site
* invite repositories of external librararies (``libavc1394``, ``libdc1394``)
* Announcement to distribution package maintainers about the upstream shift
* 2027, 2028
* Close announcement to below applications
* `FFMPEG <https://ffmpeg.org/>`_
* `GStreamer <https://gstreamer.freedesktop.org/>`_
* `VLC <https://www.videolan.org/vlc/index.ja.html>`_
* `MythTV <https://www.mythtv.org/>`_
* `FFADO <http://ffado.org/>`_
* 2029
* Close the project
* Close the communication channels
* Archive repositories
* Resign the subsystem maintainer
> > ---
> > MAINTAINERS | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 8d5bc223f..e137c1b2f 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -7954,10 +7954,11 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core-2.6.git master
> > F: drivers/target/sbp/
> >
> > FIREWIRE SUBSYSTEM
> > -M: Stefan Richter <stefanr@s5r6.in-berlin.de>
> > +M: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> > +M: Takashi Sakamoto <takaswie@kernel.org>
> > L: linux1394-devel@lists.sourceforge.net
> > S: Maintained
> > -W: http://ieee1394.wiki.kernel.org/
> > +W: http://ieee1394.docs.kernel.org/
> > T: git git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git
> > F: drivers/firewire/
> > F: include/linux/firewire.h
>
>
>
> --
> Stefan Richter
> -======--=== --== -=-=-
> http://arcgraph.de/sr/
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2023-03-11 8:03 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 [this message]
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
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=20230311080343.GA378828@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=broonie@kernel.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 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.