Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753451AbcK0Uic (ORCPT ); Sun, 27 Nov 2016 15:38:32 -0500 Received: from mail-qk0-f193.google.com ([209.85.220.193]:33921 "EHLO mail-qk0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752641AbcK0UiX (ORCPT ); Sun, 27 Nov 2016 15:38:23 -0500 MIME-Version: 1.0 X-Originating-IP: [173.13.129.225] In-Reply-To: <1479320365-27960-1-git-send-email-bleung@chromium.org> References: <1479320365-27960-1-git-send-email-bleung@chromium.org> From: Olof Johansson Date: Sun, 27 Nov 2016 12:38:21 -0800 Message-ID: Subject: Re: [PATCH] platform/chrome : Add myself as Maintainer To: Benson Leung , Darren Hart Cc: Guenter Roeck , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1332 Lines: 29 On Wed, Nov 16, 2016 at 10:19 AM, Benson Leung 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 Acked-by: Olof Johansson 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