From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Hans de Goede" <hdegoede@redhat.com>
Cc: "markgross@kernel.org" <markgross@kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] platform/x86: think-lmi: Correct NVME password handling
Date: Thu, 25 May 2023 15:45:58 -0400 [thread overview]
Message-ID: <dcb86bf8-f83c-459e-8170-b01a96ef5690@app.fastmail.com> (raw)
In-Reply-To: <e5c4c61c-a3a3-97d0-ad50-8c5b345dc334@redhat.com>
On Thu, May 25, 2023, at 3:43 PM, Hans de Goede wrote:
> Hi,
>
> On 5/25/23 21:39, Mark Pearson wrote:
>> Hi Hans,
>>
>> My apologies - I completely forgot to add the v2 tag on this patch series...had a complete brain fart.
>
> No worries I did not even notice the v2 was missing,
> my brain automatically added it :)
>
>> I assume I should resend them all - correctly named.
>
> Well I have some review remarks on patch 5/5, it would be good if you
> can address those (if you agree with them) and then lets jump straight
> to v3 to avoid confusion ?
>
Works for me :)
Mark
next prev parent reply other threads:[~2023-05-25 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 19:31 [PATCH 1/5] platform/x86: think-lmi: Enable opcode support on BIOS settings Mark Pearson
2023-05-25 19:31 ` [PATCH 2/5] platform/x86: think-lmi: Correct System password interface Mark Pearson
2023-05-25 19:31 ` [PATCH 3/5] platform/x86: think-lmi: Correct NVME password handling Mark Pearson
2023-05-25 19:39 ` Mark Pearson
2023-05-25 19:43 ` Hans de Goede
2023-05-25 19:45 ` Mark Pearson [this message]
2023-05-25 19:31 ` [PATCH 4/5] platform/x86: think-lmi: Don't display unnecessary authentication settings Mark Pearson
2023-05-25 19:31 ` [PATCH 5/5] platform/x86: think-lmi: mutex protection around multiple WMI calls Mark Pearson
2023-05-25 19:41 ` Hans de Goede
2023-05-25 19:50 ` Mark Pearson
2023-05-26 8:12 ` Hans de Goede
2023-05-26 14:00 ` Mark Pearson
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=dcb86bf8-f83c-459e-8170-b01a96ef5690@app.fastmail.com \
--to=mpearson-lenovo@squebb.ca \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--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®