linux-kernel - Re: [PATCH] MAINTAINERS: move Milo Kim to credits

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]

Date:   Tue, 22 Sep 2020 09:08:37 +0200
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Pavel Machek <pavel@....cz>
Cc:     Jonathan Cameron <jic23@...nel.org>, Dan Murphy <dmurphy@...com>,
        Lee Jones <lee.jones@...aro.org>,
        Sebastian Reichel <sre@...nel.org>,
        Mark Brown <broonie@...nel.org>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
        linux-iio@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-leds@...r.kernel.org, linux-pm@...r.kernel.org,
        dri-devel@...ts.freedesktop.org, linux-fbdev@...r.kernel.org,
        linux-pwm@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: move Milo Kim to credits

On Mon, 21 Sep 2020 at 23:06, Pavel Machek <pavel@....cz> wrote:
>
> Hi!
>
> > Milo Kim's email in TI bounces with permanent error (550: Invalid
> > recipient).  Last email from him on LKML was in 2017.  Move Milo Kim to
> > credits and remove the separate driver entries for:
> >
> >  - TI LP855x backlight driver,
> >  - TI LP8727 charger driver,
> >  - TI LP8788 MFD (ADC, LEDs, charger and regulator) drivers.
> >
> > Signed-off-by: Krzysztof Kozlowski <krzk@...nel.org>
>
> I believe normal way would be to mark the entries "orphaned", not to
> drop them altogether. Plus, I believe someone from TI is likely to
> step up.

These are entries for specific drivers so they are covered by the
subsystem maintainers. You believe someone will step up, I believe if
these were important for TI, they would find the person some time ago,
so the emails won't bounce... This was similar with BQ chargers where
Andrew's email was bouncing and after a few weeks it was fixed. To me
it looks like TI does not have any priority in maintaining separate
driver entries so what is the point to keep orphaned driver-entry? It
is not the case where we have an orphaned subsystem and we look for a
person to handle it...

Best regards,
Krzysztof