Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp1154744pxu; Thu, 8 Oct 2020 04:56:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx+Q1GA6hGBqYV+oDgB+b0NSAZx6sm18s7xAJt1JKO2nt3V3eW+pFR/+PpPKSX4u7NVfec7 X-Received: by 2002:a17:906:3399:: with SMTP id v25mr8220662eja.51.1602158174462; Thu, 08 Oct 2020 04:56:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602158174; cv=none; d=google.com; s=arc-20160816; b=kz2QD1Ro+ES/qwMBHYbwvspfWuqMCj4ufjB0DaueOwXZD/Zps9Y4yEr53EyKKqO0gb BVL0M+EmMPVPQDjpadp2wl0qbELBCQ24lQoEOn75c6J0fB9OKwVNHryoebqmnDcdt/Aj t/qcyAQcAS0ArvGzR7doY7RGxEm70UkEweAAN3Xuk/cg8pCNP9FIzc0H98zNahq4RxLh 2miM77SdBrvCy/qZUb1kIsYCFfhb6Mq1tWRTkF26IaXmrl33gXX853c/oSV4JRm64mp7 EEfBZME/+Z3uBHyqeSGkPr+BV5wbRKRw2cD9ssSOMeN6MV/2xyD7mWeQbZ4BRPgw6q1P C5mQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=sPP/9V0uyRXp+Z6vdn5kqxJQA3/F3PuAhbOknmvzZjQ=; b=vr+U+l2bMVFWm+J5kLImWGLDx8KCzn8cc+A63ntVowewbfME4qBEWsXaaL8iGIHy6N ykAV24bWucCw+gJkIDxRCj3ZdvENYbYACArsbKHj4wmnkygMHv7i+rASpiYypOOMAnbq 4QyWJL+wi82ythpb4+rAdEwgtUnAYuFLwFVcRy9JusgPttpemjJTjRqr+cPgrnNaULad mmJt6hoTqaAjqwPyHCOjo3e7PKeC4puErtBnd9L+JJxmbiCLoNNP6pqmBwKkXXxZwwCn cSv5MTQGCOgcFh5H+tBwg/lwIavTWq17pC0eUJPUb8h71h1Giiqz7BTMZdGRw8QPVixk Xv7A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="a67aoc/y"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 65si3433739edc.222.2020.10.08.04.55.50; Thu, 08 Oct 2020 04:56:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="a67aoc/y"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729566AbgJHLoH (ORCPT + 99 others); Thu, 8 Oct 2020 07:44:07 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:55493 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726099AbgJHLoH (ORCPT ); Thu, 8 Oct 2020 07:44:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1602157445; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sPP/9V0uyRXp+Z6vdn5kqxJQA3/F3PuAhbOknmvzZjQ=; b=a67aoc/yPCdjERdsEoYvT3P0m4MyrO50THrUr1hmBbzxH1xKWk25qzcq6X7G8PiQEQNvqz E8naUsQblnbXfQxCHRDEIVnYUFtxkSpkqOOMSnjmgtPosv1oh9YUNAEfdVA/5ioJOKJrjq jC6AZwTp3EyOP78Bw/nqG14tAAIR4Rw= Received: from mail-ej1-f71.google.com (mail-ej1-f71.google.com [209.85.218.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-321-plmNjv9hNNykRY3WI9uUBA-1; Thu, 08 Oct 2020 07:44:03 -0400 X-MC-Unique: plmNjv9hNNykRY3WI9uUBA-1 Received: by mail-ej1-f71.google.com with SMTP id b17so2104469ejb.20 for ; Thu, 08 Oct 2020 04:44:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=sPP/9V0uyRXp+Z6vdn5kqxJQA3/F3PuAhbOknmvzZjQ=; b=dTrMrlAKBZw07/lzPMYCOdavTGnV8pUrfoARX3FDNhd6kn7asqxKhKPPdv5aI0iEpZ IQ1x2B5My9X3jLuvvUxmtTRJJi5Ugju19CLGzZ4SzLJRIdGWeX/hYrufjZ3Nb9ntKRXb qFGzz+i7lOYb78qEl8OKBmDCFlK4KElDxlire04+BsgaZcfi1Vh/XwCgnf+NSe3N8CuU e1GxbxAVsu0bmrj65zeXDHdRGtr0MLsclUbtyv8XvYVydlxp8VvUOQ/EZoN3vszyiIQV 96XhFbyCqLtgn57bKX9SZeiYvmsL/NzYdiCIXj9e0B3DAQvTuw7+7oiBFluZX8Il9Rek +fSg== X-Gm-Message-State: AOAM533lu7GZzvvCRZazfibPPpWyW6RyfHE+WCmN8eLsli/cnQACrbcN lT/Ss/M5NdSD1Fyem9mHOhIDkqEmc6i2sngGCPejeNF0FYwyl28rLLTo2BH5KMTKvFWvaVqXSc4 Ky1Af4FW6Qe9A5dwALgVJuqZY X-Received: by 2002:aa7:c9c3:: with SMTP id i3mr8699567edt.236.1602157441985; Thu, 08 Oct 2020 04:44:01 -0700 (PDT) X-Received: by 2002:aa7:c9c3:: with SMTP id i3mr8699547edt.236.1602157441717; Thu, 08 Oct 2020 04:44:01 -0700 (PDT) Received: from x1.localdomain (2001-1c00-0c0c-fe00-d2ea-f29d-118b-24dc.cable.dynamic.v6.ziggo.nl. [2001:1c00:c0c:fe00:d2ea:f29d:118b:24dc]) by smtp.gmail.com with ESMTPSA id 1sm3800602edy.89.2020.10.08.04.44.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 08 Oct 2020 04:44:00 -0700 (PDT) Subject: Re: [PATCH v2 0/5] platform/surface: Create a platform subdirectory for Microsoft Surface devices To: Maximilian Luz , platform-driver-x86@vger.kernel.org Cc: Andy Shevchenko , Darren Hart , Mark Gross , Mika Westerberg , Gayatri Kammela , Enric Balletbo i Serra , =?UTF-8?Q?Bla=c5=be_Hrastnik?= , Stephen Just , Dan Carpenter , Benjamin Tissoires , Chen Yu , linux-kernel@vger.kernel.org References: <20201005160307.39201-1-luzmaximilian@gmail.com> From: Hans de Goede Message-ID: Date: Thu, 8 Oct 2020 13:44:00 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20201005160307.39201-1-luzmaximilian@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Maximilian, On 10/5/20 6:03 PM, Maximilian Luz wrote: > As has come up in the discussion around > > [RFC PATCH] Add support for Microsoft Surface System Aggregator Module > > it may make sense to add a Microsoft Surface specific platform > subdirectory. Andy has suggested drivers/platform/surface for that. > This series follows said suggestion and creates that subdirectory, as > well as moves Microsoft Surface related drivers over to it and updates > their MAINTAINERS entries (if available) accordingly. > > This series does not modify any existing driver code, symbols, or help > text. In case you do not know I'm taking over from any as drivers/platform/x86 maintainer. I'm fine with the concept of this series, but who is going to maintain this new drivers/platform/surface directory ? Ah I see that the first patch answers that question and the plan is to keep this part of the pdx86 maintainership. I would prefer for the new dir to have its own MAINTAINERS entry if I'm honest, I would like to try and split maintainership for the surface stuff as follows: 1. Who will review (and add their Reviewed-by or ask for improvements or nack) patches to files in this dir? 2. Who will gather approved patches apply them to a for-next branch and send them out to Linus during the merge Window? I can pick up 2. but I could really use some help with 1. So I was thinking having a separate MAINTAINERS entry for the new dir with you (Maximilian) (and me and Mark Gross) listed as MAINTAINERS; and then I'm hoping that you can do the review of surface related patches. At least those which you have not written yourself. How does that sound ? Regards, Hans > Link to discussion: > https://lore.kernel.org/lkml/CAHp75Vfp86h38Rd-VEgER7ASADdmz5ymAkuHvD0Q6WPDqZBqHw@mail.gmail.com/ > > Cc: Andy Shevchenko > > Changes in v2: > - Rebase onto linux-platform-drivers-x86/for-next to incorporate > changes in Maintainer file. > > For more details regarding changes, refer to the individual patches. > > Maximilian Luz (5): > platform: Add Surface platform directory > platform/surface: Move Surface 3 WMI driver to platform/surface > platform/surface: Move Surface 3 Button driver to platform/surface > platform/surface: Move Surface 3 Power OpRegion driver to > platform/surface > platform/surface: Move Surface Pro 3 Button driver to platform/surface > > MAINTAINERS | 3 +- > drivers/platform/Kconfig | 2 + > drivers/platform/Makefile | 1 + > drivers/platform/surface/Kconfig | 49 +++++++++++++++++++ > drivers/platform/surface/Makefile | 10 ++++ > .../platform/{x86 => surface}/surface3-wmi.c | 0 > .../{x86 => surface}/surface3_button.c | 0 > .../{x86 => surface}/surface3_power.c | 0 > .../{x86 => surface}/surfacepro3_button.c | 0 > drivers/platform/x86/Kconfig | 31 ------------ > drivers/platform/x86/Makefile | 6 --- > 11 files changed, 64 insertions(+), 38 deletions(-) > create mode 100644 drivers/platform/surface/Kconfig > create mode 100644 drivers/platform/surface/Makefile > rename drivers/platform/{x86 => surface}/surface3-wmi.c (100%) > rename drivers/platform/{x86 => surface}/surface3_button.c (100%) > rename drivers/platform/{x86 => surface}/surface3_power.c (100%) > rename drivers/platform/{x86 => surface}/surfacepro3_button.c (100%) >