2023-03-06 04:00:44

by Takashi Sakamoto

[permalink] [raw]
Subject: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

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 <[email protected]>
---
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 <[email protected]>
+M: Takashi Sakamoto <[email protected]>
+M: Takashi Sakamoto <[email protected]>
L: [email protected]
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
--
2.37.2



2023-03-06 22:18:02

by Randy Dunlap

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

Hi,

On 3/5/23 19:58, 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.

I agree that some change needs to be made. Thank you for offering.

Acked-by: Randy Dunlap <[email protected]>

> 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 <[email protected]>
> ---
> 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 <[email protected]>
> +M: Takashi Sakamoto <[email protected]>
> +M: Takashi Sakamoto <[email protected]>
> L: [email protected]
> 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

--
~Randy

2023-03-09 14:15:13

by Takashi Iwai

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

On Mon, 06 Mar 2023 04:58:14 +0100,
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 <[email protected]>

Acked-by: Takashi Iwai <[email protected]>


thanks,

Takashi

2023-03-10 20:08:19

by Stefan Richter

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

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 <[email protected]>

Acked-by: Stefan Richter <[email protected]>
> ---
> 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 <[email protected]>
> +M: Takashi Sakamoto <[email protected]>
> +M: Takashi Sakamoto <[email protected]>
> L: [email protected]
> 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/

2023-03-11 08:03:57

by Takashi Sakamoto

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

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 <[email protected]>
>
> Acked-by: Stefan Richter <[email protected]>

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 <[email protected]>
> > +M: Takashi Sakamoto <[email protected]>
> > +M: Takashi Sakamoto <[email protected]>
> > L: [email protected]
> > 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

2023-03-11 09:19:21

by Stefan Richter

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

On Mar 11 Takashi Sakamoto wrote:
> 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.

Thank you. I need to apologize that I neglected to (at least) drop my
maintainership title myself. I should have done so when I started to
realize that I am not able to fulfill this role anymore.

> 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/>`_

Do you plan to re-use the existing (but neglected, by me) repos at
kernel.org?
https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git
https://git.kernel.org/pub/scm/libs/ieee1394/libraw1394.git
https://git.kernel.org/pub/scm/libs/ieee1394/libiec61883.git

If so, is there something which I can do to transfer access to you?
(Although if yes, before that I need to enable myself to send encrypted
e-mails again, after both of the mail user agents which I use dropped gpg
support. Maybe the kernel.org admins can assist you quicker with repo
access than I might.)

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

It's good to see you being active in the kernel and related userland
development/ maintainership, and that you have a plan for the next years.
--
Stefan Richter
-======--=== --== -=-==
http://arcgraph.de/sr/

2023-03-12 07:07:42

by Takashi Sakamoto

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

Hi,

On Sat, Mar 11, 2023 at 10:15:54AM +0100, Stefan Richter wrote:
> On Mar 11 Takashi Sakamoto wrote:
> > 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.
>
> Thank you. I need to apologize that I neglected to (at least) drop my
> maintainership title myself. I should have done so when I started to
> realize that I am not able to fulfill this role anymore.
>
> > 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/>`_
>
> Do you plan to re-use the existing (but neglected, by me) repos at
> kernel.org?
> https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git
> https://git.kernel.org/pub/scm/libs/ieee1394/libraw1394.git
> https://git.kernel.org/pub/scm/libs/ieee1394/libiec61883.git
>
> If so, is there something which I can do to transfer access to you?
> (Although if yes, before that I need to enable myself to send encrypted
> e-mails again, after both of the mail user agents which I use dropped gpg
> support. Maybe the kernel.org admins can assist you quicker with repo
> access than I might.)

In the last week after posting the patch, I sent a request to system
administrator of kernel.org for the purpose. I think it will be done
within a few days so nothing left to us.

> > * 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
>
> It's good to see you being active in the kernel and related userland
> development/ maintainership, and that you have a plan for the next years.

At the moment, I have a problem about the list archive.

As you know, kernel development process heavily relies on mail. Recently
many developers use lore.kernel.org to store blasted message as
persistent storage. I would like to follow to it.

According to the documentation[1], the list archive should be prepared
including sent messages as much as possible. However I subscribed it Feb
2011 and sometimes lost messages.

I think you have the stock of enough amount of messages in your mail
box. If you have enough free time, I would ask you to create list
archive for the purpose.

[1] https://korg.docs.kernel.org/lore.html


Regards

Takashi Sakamoto

2023-04-10 00:01:38

by Randy Dunlap

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

Hi--

On 3/11/23 23:07, Takashi Sakamoto wrote:
> Hi,
>
>>
>> It's good to see you being active in the kernel and related userland
>> development/ maintainership, and that you have a plan for the next years.
>
> At the moment, I have a problem about the list archive.

If there is still a problem about the mailing list archives,
Hank Leininger at marc.info has been pretty good in the past about providing
archives fore lore.kernel.org.
See the bottom of https://marc.info/?q=about for his email address.


Are you waiting for the kernel.org account before merging the update to the
MAINTAINER's file?

thanks again.
--
~Randy

2023-04-17 14:23:32

by Takashi Sakamoto

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

Hi Randy,

I'm sorry that I didn't notice your reply, but I'm off from the receivers
list of the message.

> Hi--
>
>On 3/11/23 23:07, Takashi Sakamoto wrote:
>> Hi,
>>
>>>
>>> It's good to see you being active in the kernel and related userland
>>> development/ maintainership, and that you have a plan for the next years.
>>
>> At the moment, I have a problem about the list archive.
>
> If there is still a problem about the mailing list archives,
> Hank Leininger at marc.info has been pretty good in the past about providing
> archives fore lore.kernel.org.
> See the bottom of https://marc.info/?q=about for his email address.

Thanks for the information. As a quick glimpse, linux1394-devel has been
archived since 2003. It looks to be a good source to push into
lore.kernel.org, while I know that the list archive should include many
spams since any one is allowed to post to the list without subscribing and
being moderated at one time. It is one of my reason not to use the list
so actively. I need to make filter to remove them before pushing.
Furthermore, the ownership of list is still unclear to me. I have a small
hesitation to use it further...

> Are you waiting for the kernel.org account before merging the update to the
> MAINTAINER's file?

I've already got the account and enough permission to linux1394
repository, but The repository is inactive so long, and abandoned. Looking
ahead to my future work, I'm preparing them at present.


Thanks

Takashi Sakamoto

2023-04-20 16:04:41

by Takashi Sakamoto

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

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 <[email protected]>
> ---
> 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