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] [day] [month] [year] [list]
Message-ID: <20210211122032.00005d13@Huawei.com>
Date:   Thu, 11 Feb 2021 12:20:32 +0000
From:   Jonathan Cameron <Jonathan.Cameron@...wei.com>
To:     Krzysztof Kozlowski <krzk@...nel.org>
CC:     Lee Jones <lee.jones@...aro.org>, Dan Murphy <dmurphy@...com>,
        <linux-kernel@...r.kernel.org>, Sebastian Reichel <sre@...nel.org>,
        "Daniel Thompson" <daniel.thompson@...aro.org>,
        Mark Brown <broonie@...nel.org>,
        Jingoo Han <jingoohan1@...il.com>
Subject: Re: [RESEND PATCH v3] MAINTAINERS: add Dan Murphy as TI LP8xxx
 drivers maintainer

On Thu, 11 Feb 2021 10:05:16 +0100
Krzysztof Kozlowski <krzk@...nel.org> wrote:

> On Thu, Feb 11, 2021 at 09:03:27AM +0000, Lee Jones wrote:
> > On Wed, 10 Feb 2021, Krzysztof Kozlowski wrote:
> >   
> > > On Wed, Feb 10, 2021 at 11:33:49AM -0600, Dan Murphy wrote:  
> > > > Krzysztof
> > > > 
> > > > On 2/10/21 11:29 AM, Krzysztof Kozlowski wrote:  
> > > > > 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 add Dan Murphy from TI to look after:
> > > > >   - 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>
> > > > > Cc: Dan Murphy <dmurphy@...com>  
> > > > 
> > > > Unfortunately I need to remove my ACK.  My TI email will be disabled this
> > > > Friday.
> > > > 
> > > > No replacement has been identified  
> > > 
> > > Ah, then I propose to mark entries as orphaned - without any maintainer.
> > > Other option is to remove them entirely so they will be covered by
> > > regular power supply entry.
> > > 
> > > Any preferences here?  
> > 
> > Counter-proposal: Since they are driver-level entries, just remove
> > them altogether.  They are not orphaned as they will still come under
> > the subsystem umbrella.  
> 
> I also vote for this (that was actually my v1 of this patch).
> 
> Best regards,
> Krzysztof
> 

Likewise, fine with just dropping the entries.

Jonathan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ