public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Kurt Borja <kuurtb@gmail.com>,
	platform-driver-x86@vger.kernel.org,  Armin Wolf <W_Armin@gmx.de>,
	Mario Limonciello <mario.limonciello@amd.com>,
	 Hans de Goede <hdegoede@redhat.com>,
	Dell.Client.Kernel@dell.com,  LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 10/14] platform/x86: Add alienware-wmi.h
Date: Tue, 11 Feb 2025 18:51:03 +0200 (EET)	[thread overview]
Message-ID: <2c56e2de-02eb-d653-987f-69e674aab3c7@linux.intel.com> (raw)
In-Reply-To: <Z6t-msAAi1lVHzN9@black.fi.intel.com>

On Tue, 11 Feb 2025, Andy Shevchenko wrote:

> On Fri, Feb 07, 2025 at 10:46:06AM -0500, Kurt Borja wrote:
> > Add a header file for alienware-wmi with shared resources to support the
> > upcoming file split.
> 
> ...
> 
> >  static const struct attribute_group *alienfx_groups[] = {
> >  	&zone_attribute_group,
> > -	&hdmi_attribute_group,
> > -	&amplifier_attribute_group,
> > -	&deepsleep_attribute_group,
> > +	WMAX_DEV_GROUPS
> >  	NULL
> 
> I don't like this change as it makes code harder to understand (at one glance
> you can't answer the question "what are the groups that being listed here?".

Over having #ifdeffery here, I've no problem whatsoever with it (and in 
fact I suggested goingthis way). It's pretty much boilerplate anyway 
having to list them yet in another place.

-- 
 i.


  reply	other threads:[~2025-02-11 16:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 15:45 [PATCH v10 00/14] platform/x86: alienware-wmi driver rework Kurt Borja
2025-02-07 15:45 ` [PATCH v10 01/14] platform/x86: alienware-wmi: Add a state container for LED control feature Kurt Borja
2025-02-07 15:45 ` [PATCH v10 02/14] platform/x86: alienware-wmi: Add WMI Drivers Kurt Borja
2025-02-11 16:30   ` Andy Shevchenko
2025-02-11 17:46     ` Kurt Borja
2025-02-11 18:51       ` Andy Shevchenko
2025-02-07 15:45 ` [PATCH v10 03/14] platform/x86: alienware-wmi: Add a state container for thermal control methods Kurt Borja
2025-02-07 15:46 ` [PATCH v10 04/14] platform/x86: alienware-wmi: Refactor LED " Kurt Borja
2025-02-11 16:33   ` Andy Shevchenko
2025-02-11 17:47     ` Kurt Borja
2025-02-07 15:46 ` [PATCH v10 05/14] platform/x86: alienware-wmi: Refactor hdmi, amplifier, deepslp methods Kurt Borja
2025-02-11 16:37   ` Andy Shevchenko
2025-02-11 17:51     ` Kurt Borja
2025-02-11 18:55       ` Andy Shevchenko
2025-02-07 15:46 ` [PATCH v10 06/14] platform/x86: alienware-wmi: Refactor thermal control methods Kurt Borja
2025-02-07 15:46 ` [PATCH v10 07/14] platform/x86: alienware-wmi: Split DMI table Kurt Borja
2025-02-11 16:39   ` Andy Shevchenko
2025-02-11 17:53     ` Kurt Borja
2025-02-07 15:46 ` [PATCH v10 08/14] MAINTAINERS: Update ALIENWARE WMI DRIVER entry Kurt Borja
2025-02-07 15:46 ` [PATCH v10 09/14] platform/x86: Rename alienware-wmi.c Kurt Borja
2025-02-11 16:41   ` Andy Shevchenko
2025-02-11 17:31     ` Kurt Borja
2025-02-11 18:50       ` Andy Shevchenko
2025-02-07 15:46 ` [PATCH v10 10/14] platform/x86: Add alienware-wmi.h Kurt Borja
2025-02-11 16:45   ` Andy Shevchenko
2025-02-11 16:51     ` Ilpo Järvinen [this message]
2025-02-11 17:19       ` Andy Shevchenko
2025-02-11 17:53     ` Kurt Borja
2025-02-07 15:46 ` [PATCH v10 11/14] platform/x86: Split the alienware-wmi driver Kurt Borja
2025-02-11 16:56   ` Andy Shevchenko
2025-02-11 17:59     ` Kurt Borja
2025-02-11 19:04       ` Andy Shevchenko
2025-02-14 22:21         ` Kurt Borja
2025-02-16 20:35           ` Andy Shevchenko
2025-02-07 15:46 ` [PATCH v10 12/14] platform/x86: dell: Modify Makefile alignment Kurt Borja
2025-02-11 16:56   ` Andy Shevchenko
2025-02-07 15:46 ` [PATCH v10 13/14] platform/x86: Update alienware-wmi config entries Kurt Borja
2025-02-07 15:46 ` [PATCH v10 14/14] platform/x86: alienware-wmi: Update header and module information Kurt Borja
2025-02-10 11:53 ` [PATCH v10 00/14] platform/x86: alienware-wmi driver rework Ilpo Järvinen
2025-02-10 13:48   ` Kurt Borja
2025-02-11 16:58     ` Andy Shevchenko
2025-02-11 18:09       ` Kurt Borja

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=2c56e2de-02eb-d653-987f-69e674aab3c7@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=W_Armin@gmx.de \
    --cc=andriy.shevchenko@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=kuurtb@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.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