From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: think-lmi: Fix password opcode ordering for workstations
Date: Tue, 13 Feb 2024 14:52:16 +0200 (EET) [thread overview]
Message-ID: <7aa1ac00-0db4-934a-94d5-b5daacaeb863@linux.intel.com> (raw)
In-Reply-To: <c4e6d61d-d836-4a79-a89d-141f92f6b41e@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Fri, 9 Feb 2024, Mark Pearson wrote:
> Thanks Ilpo
>
> On Fri, Feb 9, 2024, at 10:34 AM, Ilpo Järvinen wrote:
> > On Fri, 9 Feb 2024, Mark Pearson wrote:
> >
> >> The Lenovo workstations require the password opcode to be run before
> >> the attribute value is changed (if Admin password is enabled).
> >>
> >> Tested on some Thinkpads to confirm they are OK with this order too.
> >>
> >> Signed-off-by: Mark Pearson <mpearson-lenovo@squebb.ca>
> >
> > Would a Fixes tag be appropriate here?
>
> Hmmm - good point, though it has been "wrong" since it was originally implemented (where we tested on Thinkpads).
>
> I guess I could use the commit ID from when I originally implemented opcodes?
> Fixes: 640a5fa ("platform/x86: think-lmi: Opcode support")
Yes, in that case the original commit is the correct one.
> Do you want me to push a new version with this?
I think this is simple enough to go through fixes branch so it depends on
Hans.
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
i.
next prev parent reply other threads:[~2024-02-13 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 15:23 [PATCH] platform/x86: think-lmi: Fix password opcode ordering for workstations Mark Pearson
2024-02-09 15:34 ` Ilpo Järvinen
2024-02-09 16:23 ` Mark Pearson
2024-02-13 12:52 ` Ilpo Järvinen [this message]
2024-02-19 11:36 ` Hans de Goede
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=7aa1ac00-0db4-934a-94d5-b5daacaeb863@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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