linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Maximilian Luz <luzmaximilian@gmail.com>,
	platform-driver-x86@vger.kernel.org
Cc: "Andy Shevchenko" <andy.shevchenko@gmail.com>,
	"Darren Hart" <dvhart@infradead.org>,
	"Mark Gross" <mgross@linux.intel.com>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Gayatri Kammela" <gayatri.kammela@intel.com>,
	"Enric Balletbo i Serra" <enric.balletbo@collabora.com>,
	"Blaž Hrastnik" <blaz@mxxn.io>,
	"Stephen Just" <stephenjust@gmail.com>,
	"Dan Carpenter" <dan.carpenter@oracle.com>,
	"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
	"Chen Yu" <yu.c.chen@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] platform/surface: Create a platform subdirectory for Microsoft Surface devices
Date: Thu, 8 Oct 2020 13:44:00 +0200	[thread overview]
Message-ID: <a82e3aff-801d-d116-bbf4-91f3981f713b@redhat.com> (raw)
In-Reply-To: <20201005160307.39201-1-luzmaximilian@gmail.com>

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 <andy.shevchenko@gmail.com>
> 
> 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%)
> 


  parent reply	other threads:[~2020-10-08 11:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 16:03 [PATCH v2 0/5] platform/surface: Create a platform subdirectory for Microsoft Surface devices Maximilian Luz
2020-10-05 16:03 ` [PATCH v2 1/5] platform: Add Surface platform directory Maximilian Luz
2020-10-05 16:03 ` [PATCH v2 2/5] platform/surface: Move Surface 3 WMI driver to platform/surface Maximilian Luz
2020-10-05 16:03 ` [PATCH v2 3/5] platform/surface: Move Surface 3 Button " Maximilian Luz
2020-10-05 16:03 ` [PATCH v2 4/5] platform/surface: Move Surface 3 Power OpRegion " Maximilian Luz
2020-10-05 16:03 ` [PATCH v2 5/5] platform/surface: Move Surface Pro 3 Button " Maximilian Luz
2020-10-08 11:44 ` Hans de Goede [this message]
2020-10-08 12:32   ` [PATCH v2 0/5] platform/surface: Create a platform subdirectory for Microsoft Surface devices Maximilian Luz
2020-10-08 13:38     ` Hans de Goede
2020-10-08 14:05       ` Maximilian Luz
2020-10-08 14:20     ` Hans de Goede
2020-10-08 13:52   ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a82e3aff-801d-d116-bbf4-91f3981f713b@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=blaz@mxxn.io \
    --cc=dan.carpenter@oracle.com \
    --cc=dvhart@infradead.org \
    --cc=enric.balletbo@collabora.com \
    --cc=gayatri.kammela@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luzmaximilian@gmail.com \
    --cc=mgross@linux.intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=stephenjust@gmail.com \
    --cc=yu.c.chen@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).