Message ID | 20230306035814.78455-1-o-takashi@sakamocchi.jp |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:5915:0:0:0:0:0 with SMTP id v21csp1647515wrd; Sun, 5 Mar 2023 20:03:20 -0800 (PST) X-Google-Smtp-Source: AK7set8DX36MBgEOX2F0HhuKjktdkxX45ptYRF5OM5gnj9I63MdMaS1MPzPRC80/4NpGTkO/NFEj X-Received: by 2002:aa7:904f:0:b0:611:a664:8d28 with SMTP id n15-20020aa7904f000000b00611a6648d28mr8764082pfo.4.1678075400292; Sun, 05 Mar 2023 20:03:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1678075400; cv=none; d=google.com; s=arc-20160816; b=EbF+t7AVQESGdSKbwCJ/fGEedPdDjG1RLpc5iJEjvIpWhnnQvmU4dqj+LNAj3Hf35i acKVXEZIPh8wl1Z6bMzr/LhJ126PIjAm35DnpkOZ+pI5YRc0vA3BJ4oDhXGU7Z0+LANN OpL/qf4FyiEAZnnGIAvSbtw1014xyipeZPvNhK///8N6yPyzcVxO4mzCH1PFW3HYEIMD UPpgrrJcV8DhUt/HYnBiZPPSNRoldQO07ikaKHdntSWZcMU8geF4UH7eZ/eQaI8LIhi5 tdcetJ5RJtvxT5tWQYBDD81HidVbynl+jsqKvXM0q4eroscCDlf5zOc0xhyoSFm2iRI+ jT1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:feedback-id:dkim-signature :dkim-signature; bh=pnFkC+vgiukAXvQZB2Xafq5RnPPqc7XatDUtnaIu0bM=; b=Bu9Eg/43YgzATtIbiF6tbolHxETuFLT0Ya/qPh6mw4m9bX+953IzMYgqzfhesXG4GN sV+y9X/GB7HhqZM1gff8WVnGYU51QND3AE0Ha9atuuj530q9jAVF73vPueYXotg0A9yK clzvHAKiMuYDtOfTzvwXVLrLgjBstSfP0Cn7pYAZBOABKTbUILVTuVtJDDGIJiS3yR9y a3fG4FbQFnaVE+6euorn5lzXiY6fzQExzjPQkvey+iZNe3JMWSlzDurrroQSSfklZp3u L6OE9E42Wv1HNk29fXeMe1cdIQAM8vrGdiei118ZkTrLCjMAagq1QSR2SrgKPaBTbBpn rSlA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sakamocchi.jp header.s=fm1 header.b=wAfpBuN9; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=M8QSy6cv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m11-20020a65438b000000b004fb96c0813dsi7766500pgp.344.2023.03.05.20.03.07; Sun, 05 Mar 2023 20:03:20 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sakamocchi.jp header.s=fm1 header.b=wAfpBuN9; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=M8QSy6cv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229663AbjCFD60 (ORCPT <rfc822;toshivichauhan@gmail.com> + 99 others); Sun, 5 Mar 2023 22:58:26 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32822 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229457AbjCFD6X (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Sun, 5 Mar 2023 22:58:23 -0500 Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 72643D31E for <linux-kernel@vger.kernel.org>; Sun, 5 Mar 2023 19:58:22 -0800 (PST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1FA435C00B7; Sun, 5 Mar 2023 22:58:20 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 05 Mar 2023 22:58:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sakamocchi.jp; h=cc:cc:content-transfer-encoding:content-type:date:date:from :from:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to; s=fm1; t=1678075100; x=1678161500; bh=pn FkC+vgiukAXvQZB2Xafq5RnPPqc7XatDUtnaIu0bM=; b=wAfpBuN9DcC+29wxaV /DlKN6CVi0qSvZLb6DXDmlt9SbKx5TEMcazj7xUTxv0/w/iRUJ99+rWTbMwM+o4i E1OgqWhRa2sPcI5MmNFc4MbBimHpwtkV2EATAIb39sqb/dLq6AEQAVOWnBuFb7F+ PaINwtjVNAXqcd/60uL67Twomhcz4OegNn3OPh7qU87KLkwlSy4g8cl6E88W2Udt tDtE9mUmuWZyggtx2CB8xb6Uwz++p2Syv6rw6Lk/f59lrg72p50fseT/tLjpo+0Q jNv959Uai+IqkQt1tsV3TDSn5k1d9Uh6tCMlrAE+TzW/xzYKdvCgFYzsiVn0KShM LD+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1678075100; x=1678161500; bh=pnFkC+vgiukAX vQZB2Xafq5RnPPqc7XatDUtnaIu0bM=; b=M8QSy6cvCjxwX/ehr9AZTKKZlx4j/ 2qGQ8A21zDexblRjCWHyw+K6C84sGPBoPdb/ZZUmv5ivGzIHDiI9gJgjfBaUZXFC j1qBa2IiaoUkNCUOC+6bj5E/1OyhbUbr2rTswWw98CNbir/2j/vt2BiiqtVZ02Jc WW+Y8IegfX9wdruQXrsDa4Ac2GW4vkiBlNfsx9Jn04jMKXrE/O/A6jNZvEPvvFh7 Sh2bt88LD2MZv3pB0l4tMtNNLdqqK00xdJkwWXec1z9+cBi9XJ/R2CVvd/6Q4g2V YdTagofuIiu5VXBVRi9TxBgpcfulgICnyajxfCXtuPvYjpLr3Hf06bulg== X-ME-Sender: <xms:22QFZFkAntOVfyq_W0t20ZcRzDojHiR0fbDdcL4Sqk1EmEV0peVKuQ> <xme:22QFZA04mNadzesFnyAxg1THeWYL2V6yhN-VQVYxkvLU8ACh6h-fT9BWuSsMT0XH_ 0vcpk91pdRGz2AyfPI> X-ME-Received: <xmr:22QFZLrjhwrEkEPcflMOv8Z9eUbPY9nqKE38ExVYY1oTCJ7Vux-gTyQUUUFztaWlblK0phEBd1lNfVfqXBrC1X_RmJoY6rrK8dUkT7zvMUz6> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddthedgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkffoggfgsedtkeertd ertddtnecuhfhrohhmpefvrghkrghshhhiucfurghkrghmohhtohcuoehoqdhtrghkrghs hhhisehsrghkrghmohgttghhihdrjhhpqeenucggtffrrghtthgvrhhnpeeggfehleehje eileehveefkefhtdeffedtfeeghfekffetudevjeegkeevhfdvueenucffohhmrghinhep khgvrhhnvghlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepohdqthgrkhgrshhhihesshgrkhgrmhhotggthhhirdhjph X-ME-Proxy: <xmx:22QFZFl-0BLUH2NhP27sZAnYsLaZUVgoLCIxhSxZHKXCJHPWoN5Ixw> <xmx:22QFZD2GmTi0dEmSPxpkkFX9tnv-RRRJ8xeIIuNQRe8nnQhuSg_ckQ> <xmx:22QFZEuSGy-jv2dqrqu8awwXrex9rI_6eEVq4K67incKef21iYJzCg> <xmx:3GQFZEzW6dGj0a3Ttnyg_xE1y5GOL-26AoPeqPDBYp0-zbSn_frkmA> Feedback-ID: ie8e14432:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 5 Mar 2023 22:58:18 -0500 (EST) 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 Subject: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem Date: Mon, 6 Mar 2023 12:58:14 +0900 Message-Id: <20230306035814.78455-1-o-takashi@sakamocchi.jp> X-Mailer: git-send-email 2.37.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1759589591120667481?= X-GMAIL-MSGID: =?utf-8?q?1759589591120667481?= |
Series |
MAINTAINERS: replace maintainer of FireWire subsystem
|
|
Commit Message
Takashi Sakamoto
March 6, 2023, 3:58 a.m. UTC
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(-)
Comments
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 <rdunlap@infradead.org> > 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(-) > > 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
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 <o-takashi@sakamocchi.jp> Acked-by: Takashi Iwai <tiwai@suse.de> thanks, Takashi
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> > --- > 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
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
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.
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
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.
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
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
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