linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maximilian Luz <luzmaximilian@gmail.com>
To: Hans de Goede <hdegoede@redhat.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 14:32:58 +0200	[thread overview]
Message-ID: <deb1c682-5843-61b1-173b-a70ef51e85f2@gmail.com> (raw)
In-Reply-To: <a82e3aff-801d-d116-bbf4-91f3981f713b@redhat.com>

On 10/8/20 1:44 PM, Hans de Goede wrote:
> 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 ?

Sounds good, I'd be happy to help review and approve any Surface related
patches. However, I think it would be beneficial if you and Mark still
have a final look (and say) over the ones I've reviewed and accepted (if
that's not already a given). I feel like I may lack a bit of experience
for this job and might miss some things.

I'll add the MAINTAINERS entry and send a v3 later today, if that's OK.

Regards,
Max

  reply	other threads:[~2020-10-08 12:33 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 ` [PATCH v2 0/5] platform/surface: Create a platform subdirectory for Microsoft Surface devices Hans de Goede
2020-10-08 12:32   ` Maximilian Luz [this message]
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=deb1c682-5843-61b1-173b-a70ef51e85f2@gmail.com \
    --to=luzmaximilian@gmail.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=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).