From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
ikepanhc@gmail.com, "Armin Wolf" <W_Armin@gmx.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
ibm-acpi-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] platform/x86: Move Lenovo files into lenovo subdir
Date: Thu, 08 May 2025 10:23:47 -0400 [thread overview]
Message-ID: <6d4f3523-0d3a-4f1a-bec9-d053fad8a509@app.fastmail.com> (raw)
In-Reply-To: <09a628d3-5903-5d5d-b874-5e77bbdf939a@linux.intel.com>
Thanks Ilpo,
On Thu, May 8, 2025, at 10:01 AM, Ilpo Järvinen wrote:
> On Wed, 7 May 2025, Mark Pearson wrote:
>
>> Move all Lenovo specific files into their own sub-directory as part
>> of clean-up exercise.
>> Longer term goal is to break-up thinkpad_acpi to improve maintainability
>> and perhaps share more functionality with other non thinkpad Lenovo
>> platforms.
>>
>> Signed-off-by: Mark Pearson <mpearson-lenovo@squebb.ca>
>> ---
>> Some questions that I didn't want to put in the commit comment:
>>
>> - I didn't know if now was a good time to propose this change. I
>> realise it could cause headaches for anybody with patches being
>> worked on.
>
> Don't worry too much about other changes, if you don't recall anything
> immediately, there likely isn't anything that significant. If we always
> postpone useful reorganizations in fear that some hypothetical work would
> have to rebase, it never gets done :-).
>
>> Please let me know what makes it easiest for maintainers
>> and other developers. If there is a particular branch that would be
>> better to do this against also let me know.
>
> Once I've merged fixes branch into for-next (I should do that at latest
> early next week if not already this week), it should be pretty
> straightforward to handle such move without conflicts.
>
OK - thanks. If there's anything I can do to help let me know.
>> - Should I be updating the MAINTAINERS file? I'm still not sure what
>> the protocol there is. I'm very happy to help review anything in the
>> lenovo directory, but I didn't want to make assumptions.
>
> You should certainly update MAINTAINERS in the same patch to the new
> paths. If you want to make other changes, put them such as add your name
> into some entry or create a generic LENOVO entry, put those into own
> patch after the move please.
>
OK - I'll submit a v2 with that change. Thanks for the guidance
>> - I have tested on multiple platforms but I don't have any ideapads I
>> can use.
>
> Given it's just moves file to new place, the threat of breaking something
> that isn't detected by simple build test, isn't that high.
>
Agreed - thanks for the review.
Mark
next prev parent reply other threads:[~2025-05-08 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 19:04 Mark Pearson
2025-05-07 19:04 ` [PATCH 2/2] platform/x86: export thinkpad_acpi handles Mark Pearson
2025-05-08 14:03 ` Ilpo Järvinen
2025-05-08 14:28 ` Mark Pearson
2025-05-08 14:32 ` Andy Shevchenko
2025-05-08 15:02 ` Mark Pearson
2025-05-08 14:31 ` Andy Shevchenko
2025-05-08 15:01 ` Mark Pearson
2025-05-08 14:01 ` [PATCH 1/2] platform/x86: Move Lenovo files into lenovo subdir Ilpo Järvinen
2025-05-08 14:23 ` Mark Pearson [this message]
2025-05-08 14:27 ` Ilpo Järvinen
2025-05-08 14:29 ` Mark Pearson
2025-05-08 14:29 ` 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=6d4f3523-0d3a-4f1a-bec9-d053fad8a509@app.fastmail.com \
--to=mpearson-lenovo@squebb.ca \
--cc=W_Armin@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=ikepanhc@gmail.com \
--cc=ilpo.jarvinen@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
all inboxes | Powered by JetHome®