X86 platform drivers
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mark Gross <mgross@linux.intel.com>, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1] platform/x86: Kconfig: Surround WMI drivers by 'if ACPI_WMI'
Date: Wed, 3 Feb 2021 13:11:43 +0100	[thread overview]
Message-ID: <c3fc4dfd-13b5-73c0-7d97-cdab0b61f170@redhat.com> (raw)
In-Reply-To: <YBqJ7VmchoG6Kt8t@smile.fi.intel.com>

Hi,

On 2/3/21 12:33 PM, Andy Shevchenko wrote:
> On Wed, Feb 03, 2021 at 11:55:40AM +0100, Hans de Goede wrote:
>> On 2/3/21 11:48 AM, Hans de Goede wrote:
>>> On 1/26/21 3:00 PM, Andy Shevchenko wrote:
>>>> Surround WMI drivers by 'if ACPI_WMI' instead of depending
>>>> each of them separately.
>>>
>>> This does not cover all drivers which depend on ACPI_WMI; and in
>>> for-next there is a new UV_SYSFS Kconfig symbol in the middle of
>>> the block which you are surrounding with if ACPI_WMI .. endif
>>> and that new Kconfig symbol does not depend on ACPI_WMI.
>>>
>>> Admittedly I should have payed more attention when the UV_SYSFS
>>> symbol was merged, but atm there is no real ordering in the
>>> Kconfig symbols.
>>
>> Ok, so I just checked the Makefile and noticed that there is
>> an ordering there. But most people start with looking at Kconfig
>> when adding a new driver and the ordering is very much not clear
>> there. Also splitting the Intel bits in three groups does not
>> necessariyl help IMHO. E.g  CONFIG_INTEL_CHT_INT33FE is in the
>> generic Intel block but it is definitely PMIC related.
>>
>> And the WMI drivers are grouped, except that some of them
>> (Asus, Dell, EEEPC at least) are not in the group...
>>
>> So I still think just sorting the entire bups alphabetically
>> is better. We can then also add a comment at the top to please
>> keep things sorted alphabetically.
> 
> In long term I prefer split the entire folder to subfolders where you create
> a new Kconfig with a rules like alphabetical order or so.
> 
> Shuffling now Kconfig and Makefile w/o above doesn't bring a value in my
> opinion.

Ok, lets keep things as is for now then and hopefully in the future
someone will have some time to clean this up a bit.

Regards,

Hans


  reply	other threads:[~2021-02-03 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 14:00 [PATCH v1] platform/x86: Kconfig: Surround WMI drivers by 'if ACPI_WMI' Andy Shevchenko
2021-02-03 10:48 ` Hans de Goede
2021-02-03 10:55   ` Hans de Goede
2021-02-03 11:33     ` Andy Shevchenko
2021-02-03 12:11       ` Hans de Goede [this message]
2021-02-03 12:16         ` Andy Shevchenko
2021-02-03 12:57           ` Hans de Goede
2021-02-03 13:45             ` 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=c3fc4dfd-13b5-73c0-7d97-cdab0b61f170@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=mgross@linux.intel.com \
    --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