linux-kernel - Re: [PATCH v2] platform/x86: Move Lenovo files into lenovo subdir

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <dd3b79e3-a0d1-4413-8c69-58ca6b4fb8c9@app.fastmail.com>
Date: Thu, 05 Jun 2025 17:03:15 -0400
From: "Mark Pearson" <mpearson-lenovo@...ebb.ca>
To: "Andy Shevchenko" <andriy.shevchenko@...ux.intel.com>
Cc: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
 "Hans de Goede" <hdegoede@...hat.com>, "Jonathan Corbet" <corbet@....net>,
 ikepanhc@...il.com, "Henrique de Moraes Holschuh" <hmh@....eng.br>,
 "Armin Wolf" <W_Armin@....de>, linux-doc@...r.kernel.org,
 "platform-driver-x86@...r.kernel.org" <platform-driver-x86@...r.kernel.org>,
 ibm-acpi-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] platform/x86: Move Lenovo files into lenovo subdir

Hi Andy

On Thu, Jun 5, 2025, at 3:43 PM, Andy Shevchenko wrote:
> On Thu, Jun 05, 2025 at 11:53:47AM -0400, Mark Pearson wrote:
>> On Thu, Jun 5, 2025, at 1:58 AM, Andy Shevchenko wrote:
>> > On Wed, Jun 04, 2025 at 01:36:53PM -0400, Mark Pearson wrote:
>> >> Create lenovo subdirectory for holding Lenovo specific drivers.
>
> ...
>
>> >> -F:	drivers/platform/x86/lenovo-wmi-hotkey-utilities.c
>> >> +F:	drivers/platform/x86/lenovo/lenovo-wmi-hotkey-utilities.c
>> >
>> > You may follow the trick in the Makefile (see intel folder) to avoid repetition
>> > of the folder name in the file names. Note, the modules will be called the
>> > same (assuming no ABI breakages due to renames).
>> >
>> Interesting - I'll have to look at that a bit more.
>> Any objections if I leave that for a future change?
>
> IF it's nearest future :-)
>
I got this implemented - I'll include it with v3. It's less complicated than I thought when I initially looked. 
Thanks for the suggestion.

Mark