linux-kernel - Re: [PATCH] platform/chrome : Add myself as Maintainer

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:   Sun, 27 Nov 2016 12:38:21 -0800
From:   Olof Johansson <olof@...om.net>
To:     Benson Leung <bleung@...omium.org>,
        Darren Hart <dvhart@...ux.intel.com>
Cc:     Guenter Roeck <linux@...ck-us.net>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] platform/chrome : Add myself as Maintainer

On Wed, Nov 16, 2016 at 10:19 AM, Benson Leung <bleung@...omium.org> wrote:
> I'll be taking over maintainership of platform/chrome from Olof,
> so let's add me to the list of maintainers.
>
> Signed-off-by: Benson Leung <bleung@...omium.org>

Acked-by: Olof Johansson <olof@...om.net>

I talked to Darren at Plumbers about drivers/platform/chrome, and
whether he was open to merge that contents through his
drivers/platform tree, and he was open to that.

Darren, meet Benson -- Benson will be picking up maintainership of the
chrome platform code since I no longer have good access to hardware to
test new changes. We didn't talk about the method of merging, if you
prefer to get patches sent directly to you or if you're OK with
merging a git branch from Benson. The latter might be easier for
Benson, the former might be easier for you.

In the past, the amount of code coming in through the platform/chrome
tree has been relatively small, it's mostly been a matter of acking
drivers going in through MFD or other trees. The main reason to split
them out to a separate platform directory has been because it cuts
across architectures and none of the previous ones were a good fit
(i.e. drivers/platform/x86 was too narrow). I expect that to stay true
as long as there are ARM Chromebooks, which is hopefully forever. :)

-Olof