From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: "platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
ibm-acpi-devel@lists.sourceforge.net, "Limonciello,
Mario" <mario.limonciello@amd.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: Add support for improved performance mode
Date: Mon, 13 Nov 2023 16:24:46 +0200 (EET) [thread overview]
Message-ID: <e2b73a2a-b1ef-9dc8-9924-f1ab2b1f5fd@linux.intel.com> (raw)
In-Reply-To: <b3167aca-032d-4ec4-b438-38416a5d8a10@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On Mon, 13 Nov 2023, Mark Pearson wrote:
> On Fri, Nov 10, 2023, at 7:37 AM, Ilpo Järvinen wrote:
> > On Thu, 9 Nov 2023, Mark Pearson wrote:
> >> On Thu, Nov 9, 2023, at 5:10 AM, Ilpo Järvinen wrote:
> >> > On Wed, 8 Nov 2023, Mark Pearson wrote:
> <snip>
> >>
> >> >
> >> > Looking into the driver a bit more, there are a few other defines which
> >> > could also move BIT() from the code into defines. Please tell if you're
> >> > going to look at those because if not, I might try to make the patches.
> >>
> >> Happy to look at doing that as I'm playing around with this driver anyway.
> >
> > Okay, thanks.
> >
> Just a quick note - I pushed v2 for this patch, and I'll tackle the
> other BIT changes separately (rather than adding it as part of a
> series). Looking through the code I wanted to spend more time on that
> piece - I'm not ignoring it :)
Yeah, no problem. I was expecting it separately anyway. :-)
--
i.
prev parent reply other threads:[~2023-11-13 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 16:20 Mark Pearson
2023-11-09 10:10 ` Ilpo Järvinen
2023-11-09 17:57 ` Mark Pearson
2023-11-10 12:37 ` Ilpo Järvinen
2023-11-13 14:00 ` Mark Pearson
2023-11-13 14:24 ` Ilpo Järvinen [this message]
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=e2b73a2a-b1ef-9dc8-9924-f1ab2b1f5fd@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mpearson-lenovo@squebb.ca \
--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®