From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1 1/1] platform/x86: Add include/linux/platform_data/x86 to MAINTAINERS
Date: Fri, 10 Feb 2023 17:16:03 +0100 [thread overview]
Message-ID: <2e959ac0-e33a-6128-4fb7-6d86fbb6f69a@redhat.com> (raw)
In-Reply-To: <20230206150202.27892-1-andriy.shevchenko@linux.intel.com>
Hi,
On 2/6/23 16:02, Andy Shevchenko wrote:
> Most of the files there are being used under PDx86 subsystem or
> tightly related drivers (like drivers/clk/x86/). I think it makes
> sense to assure that PDx86 keeps an eye on the changes there.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Thank you for your patch, I've applied this patch to my review-hans
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4329d6611c20..705ffd15afbe 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -22598,6 +22598,7 @@ S: Maintained
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git
> F: drivers/platform/olpc/
> F: drivers/platform/x86/
> +F: include/linux/platform_data/x86/
>
> X86 PLATFORM DRIVERS - ARCH
> R: Darren Hart <dvhart@infradead.org>
prev parent reply other threads:[~2023-02-10 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:02 [PATCH v1 1/1] platform/x86: Add include/linux/platform_data/x86 to MAINTAINERS Andy Shevchenko
2023-02-10 16:16 ` Hans de Goede [this message]
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=2e959ac0-e33a-6128-4fb7-6d86fbb6f69a@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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