| Message ID | 20231023032905.22515-3-bagasdotme@gmail.com (mailing list archive) |
|---|---|
| State | Changes Requested |
| Delegated to: | Netdev Maintainers |
| Headers | show |
| Series | MAINTAINERS: WWAN subsystem changes | expand |
On Mon, 23 Oct 2023 10:29:04 +0700 Bagas Sanjaya wrote:
> M Chetan Kumar <m.chetan.kumar@linux.intel.com> (commit_signer:15/23=65%,authored:14/23=61%)
14 patches authored and 15 signed off?
Let me be more clear this time - nak, please drop this patch.
On 23/10/2023 23:38, Jakub Kicinski wrote: > On Mon, 23 Oct 2023 10:29:04 +0700 Bagas Sanjaya wrote: >> M Chetan Kumar <m.chetan.kumar@linux.intel.com> (commit_signer:15/23=65%,authored:14/23=61%) > > 14 patches authored and 15 signed off? > Let me be more clear this time - nak, please drop this patch. Or maybe as well drop INTEL WWAN IOSM DRIVER entry (and let WWAN subsystem maintainers handle it)? I don't want people get their inboxes spammed with bounces against his addresses, though. He's now in a state of limbo. He has significant contribution (and gets listed by get_maintainer script with (AFAIK) no way to filter him out), yet emails to him bounces. What will be the resolution then?
On Tue, 24 Oct 2023 07:11:12 +0700 Bagas Sanjaya wrote: > > 14 patches authored and 15 signed off? > > Let me be more clear this time - nak, please drop this patch. > > Or maybe as well drop INTEL WWAN IOSM DRIVER entry (and let > WWAN subsystem maintainers handle it)? I don't want > people get their inboxes spammed with bounces against > his addresses, though. Right, sorry, still delete him from the MAINTAINERS. Just don't add him to the CREDITS. > He's now in a state of limbo. He has significant contribution > (and gets listed by get_maintainer script with (AFAIK) no way > to filter him out), yet emails to him bounces. What will be > the resolution then? Yes :( Not much we can do about that (even if we drop him from maintainers all fixes will CC him based on the sign-off tags).
On Mon, Oct 23, 2023 at 06:52:21PM -0700, Jakub Kicinski wrote: > On Tue, 24 Oct 2023 07:11:12 +0700 Bagas Sanjaya wrote: > > > 14 patches authored and 15 signed off? > > > Let me be more clear this time - nak, please drop this patch. > > > > Or maybe as well drop INTEL WWAN IOSM DRIVER entry (and let > > WWAN subsystem maintainers handle it)? I don't want > > people get their inboxes spammed with bounces against > > his addresses, though. > > Right, sorry, still delete him from the MAINTAINERS. > Just don't add him to the CREDITS. > > > He's now in a state of limbo. He has significant contribution > > (and gets listed by get_maintainer script with (AFAIK) no way > > to filter him out), yet emails to him bounces. What will be > > the resolution then? > > Yes :( Not much we can do about that (even if we drop him from > maintainers all fixes will CC him based on the sign-off tags). OK, thanks!
On Mon, 2023-10-23 at 18:52 -0700, Jakub Kicinski wrote: > > > He's now in a state of limbo. He has significant contribution > > (and gets listed by get_maintainer script with (AFAIK) no way > > to filter him out), yet emails to him bounces. What will be > > the resolution then? > > Yes :( Not much we can do about that (even if we drop him from > maintainers all fixes will CC him based on the sign-off tags). I was hoping he'd chime in here - I did manage to find him at his personal address, but I didn't want to just add his personal address to the public list. If he's OK with exposing his personal (or new work?) address I guess we could add him to the .mailmap, to address this particular problem. Anyway I've BCC'ed him now (Hi Chetan :) ), but he had also said he was checking with his new work about this all. johannes
On 24.10.23 09:40, Johannes Berg wrote: > On Mon, 2023-10-23 at 18:52 -0700, Jakub Kicinski wrote: >> >>> He's now in a state of limbo. He has significant contribution >>> (and gets listed by get_maintainer script with (AFAIK) no way >>> to filter him out), yet emails to him bounces. What will be >>> the resolution then? >> >> Yes :( Not much we can do about that (even if we drop him from >> maintainers all fixes will CC him based on the sign-off tags). > > I was hoping he'd chime in here - I did manage to find him at his > personal address, but I didn't want to just add his personal address to > the public list. > > If he's OK with exposing his personal (or new work?) address I guess we > could add him to the .mailmap, to address this particular problem. > > Anyway I've BCC'ed him now (Hi Chetan :) ), but he had also said he was > checking with his new work about this all. [reviving a old thread] Johannes, if you have a minute: did anything ever come out of that? Or did anyone else step in to take care of Intels's IOSM driver? Martian (now CCed) struggles with a problem (https://bugzilla.kernel.org/show_bug.cgi?id=218383 [no, not a regression iirc]) for a while now and is kinda stuck. We discussed off-list submitting a "mark as orphan" patch, but then I found this discussion. Ciao, Thorsten
On Mon, 14 Oct 2024, Thorsten Leemhuis wrote: > >>> He's now in a state of limbo. He has significant contribution > >>> (and gets listed by get_maintainer script with (AFAIK) no way > >>> to filter him out), yet emails to him bounces. What will be > >>> the resolution then? > >> > >> Yes :( Not much we can do about that (even if we drop him from > >> maintainers all fixes will CC him based on the sign-off tags). FWIW adding an entry to .get_maintainer.ignore is the way to sort it. Maciej
On Mon, 2024-10-14 at 10:22 +0200, Thorsten Leemhuis wrote: > > > > Anyway I've BCC'ed him now (Hi Chetan :) ), but he had also said he was > > checking with his new work about this all. > > [reviving a old thread] > > Johannes, if you have a minute: did anything ever come out of that? No, I guess I can try again, but everyone pretty much moved on from this stuff... Would be surprised if Chetan were interested in any of this now. > Or did anyone else step in to take care of Intels's IOSM driver? Not that I know of and I think the business was pretty much wound down? No idea really though. johannes
On 22.10.24 16:27, Johannes Berg wrote: > On Mon, 2024-10-14 at 10:22 +0200, Thorsten Leemhuis wrote: >>> >>> Anyway I've BCC'ed him now (Hi Chetan :) ), but he had also said he was >>> checking with his new work about this all. >> >> [reviving a old thread] >> >> Johannes, if you have a minute: did anything ever come out of that? > No, I guess I can try again, but everyone pretty much moved on from this > stuff... Would be surprised if Chetan were interested in any of this > now. > >> Or did anyone else step in to take care of Intels's IOSM driver? > Not that I know of and I think the business was pretty much wound down? > No idea really though. Thx for the reply. Then I guess it's time to mark this as orphaned in MAINTAINERS, unless anyone objects. Bagas, you about a year ago had a patch that did some of that. Want to update and resubmit it? Please include a link to this thread in the patch description. Ciao, Thorsten
diff --git a/CREDITS b/CREDITS index f33a33fd237170..0472398b6aa7e9 100644 --- a/CREDITS +++ b/CREDITS @@ -2191,6 +2191,11 @@ D: pirq addr, CS5535 alsa audio driver S: Gurgaon, India S: Kuala Lumpur, Malaysia +N: M Chetan Kumar +E: <m.chetan.kumar@intel.com> +D: Intel WWAN IOSM driver +D: Mediatek T7XX 5G WWAN reviewer + N: Mohit Kumar D: ST Microelectronics SPEAr13xx PCI host bridge driver D: Synopsys DesignWare PCI host bridge driver diff --git a/MAINTAINERS b/MAINTAINERS index 7a7bd8bd80e9f2..08a7be6a5680ed 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10879,7 +10879,6 @@ S: Maintained F: drivers/platform/x86/intel/wmi/thunderbolt.c INTEL WWAN IOSM DRIVER -M: M Chetan Kumar <m.chetan.kumar@intel.com> M: Intel Corporation <linuxwwan@intel.com> L: netdev@vger.kernel.org S: Maintained @@ -13504,7 +13503,6 @@ M: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com> M: Intel Corporation <linuxwwan@intel.com> R: Chiranjeevi Rapolu <chiranjeevi.rapolu@linux.intel.com> R: Liu Haijun <haijun.liu@mediatek.com> -R: M Chetan Kumar <m.chetan.kumar@linux.intel.com> R: Ricardo Martinez <ricardo.martinez@linux.intel.com> L: netdev@vger.kernel.org S: Supported
Emails to him bounce with 550 error code: ``` 5.1.0 - Unknown address error 550-'5.1.1 <m.chetan.kumar@linux.intel.com>: Recipient address rejected: User unknown in virtual mailbox table' ``` It looks like he had left Intel, so move him to CREDITS. Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> --- He is still listed by scripts/get_maintainer.pl, though (due to significant contribution): ``` $ scripts/get_maintainer.pl drivers/net/wwan/iosm/ ... M Chetan Kumar <m.chetan.kumar@linux.intel.com> (commit_signer:15/23=65%,authored:14/23=61%) ... ``` If no one steps up maintaining IOSM, should INTEL WWAN IOSM DRIVER entry be removed then to get rid of him, like in [1]? [1]: https://lore.kernel.org/lkml/20210316081000.12596-1-krzysztof.kozlowski@canonical.com/ CREDITS | 5 +++++ MAINTAINERS | 2 -- 2 files changed, 5 insertions(+), 2 deletions(-)