[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e745724-d704-6250-9bfb-e347f3611ec4@redhat.com>
Date: Wed, 6 Jan 2021 10:17:23 +0100
From: Hans de Goede <hdegoede@...hat.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Jiaxun Yang <jiaxun.yang@...goat.com>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <lenb@...nel.org>,
Mark Gross <mgross@...ux.intel.com>,
Ike Panhc <ike.pan@...onical.com>,
Mark Pearson <markpearson@...ovo.com>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] IdeaPad platform profile support
Hi,
On 1/5/21 6:18 PM, Rafael J. Wysocki wrote:
> On Mon, Jan 4, 2021 at 9:58 PM Hans de Goede <hdegoede@...hat.com> wrote:
<snip>
>> Patch 1/2 does use a slightly different approach then I suggest above,
>> thinking more about this it would be cleaner IMHO to just pass the
>> cur_profile pointer to the callbacks as the pseudo-code patch which I
>> wrote above does. Drivers which use globals can then just ignore
>> the extra argument (and keep the platform_profile_handler struct const)
>> where as drivers which use dynamic allocation can embed the struct in
>> their driver's data-struct.
>
> Agreed.
Note that Jiaxun has provided a v2 of this patch-set with patch 1/2 implementing
the new approach.
Can you merge merge that patch please and then once you're happy that this
has seen enough exposure in -next, provide me with an immutable branch with
the 3 platform-profile patches in it ?
Regards,
Hans
Powered by blists - more mailing lists