lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc949ab7-b5aa-4812-9c4a-d50bfee92de0@leemhuis.info>
Date: Mon, 14 Oct 2024 10:22:36 +0200
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Johannes Berg <johannes@...solutions.net>,
 Jakub Kicinski <kuba@...nel.org>, Bagas Sanjaya <bagasdotme@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Networking <netdev@...r.kernel.org>,
 Loic Poulain <loic.poulain@...aro.org>,
 Sergey Ryazanov <ryazanov.s.a@...il.com>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
 Martin Wolf <mwolf@...umentum.com>
Subject: Re: [PATCH net v2 1/2] MAINTAINERS: Move M Chetan Kumar to CREDITS

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ