mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
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 21:43:59 +0200	[thread overview]
Message-ID: <e5c4c61c-a3a3-97d0-ad50-8c5b345dc334@redhat.com> (raw)
In-Reply-To: <17963a3d-996f-4bb8-918e-aadba15be9bc@app.fastmail.com>

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 ?

> I also have no idea why they showed up out of order...I'm blaming that one on the email server.

The out of order thing is normal, this sometimes happens with email.

> Sorry :(

Again no worries / no problem ...

Regards,

Hans




> On Thu, May 25, 2023, at 3:31 PM, Mark Pearson wrote:
>> NVME passwords identifier have been standardised across the Lenovo
>> systems and now use udrp and adrp (user and admin level) instead of
>> unvp and mnvp.
>>
>> This should apparently be backwards compatible.
>>
>> Also cleaned up so the index is set to a default of 1 rather than 0
>> as this just makes more sense (there is no device 0).
>>
>> Signed-off-by: Mark Pearson <mpearson-lenovo@squebb.ca>
>> ---
>> Changes in V2: None. Version bumped in series
>>
>>  drivers/platform/x86/think-lmi.c | 8 ++++++--
>>  1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/platform/x86/think-lmi.c b/drivers/platform/x86/think-lmi.c
>> index c7e98fbe7c3d..1c02958035ad 100644
>> --- a/drivers/platform/x86/think-lmi.c
>> +++ b/drivers/platform/x86/think-lmi.c
>> @@ -456,9 +456,9 @@ static ssize_t new_password_store(struct kobject *kobj,
>>  				sprintf(pwd_type, "mhdp%d", setting->index);
>>  		} else if (setting == tlmi_priv.pwd_nvme) {
>>  			if (setting->level == TLMI_LEVEL_USER)
>> -				sprintf(pwd_type, "unvp%d", setting->index);
>> +				sprintf(pwd_type, "udrp%d", setting->index);
>>  			else
>> -				sprintf(pwd_type, "mnvp%d", setting->index);
>> +				sprintf(pwd_type, "adrp%d", setting->index);
>>  		} else {
>>  			sprintf(pwd_type, "%s", setting->pwd_type);
>>  		}
>> @@ -1524,6 +1524,10 @@ static int tlmi_analyze(void)
>>  		if (!tlmi_priv.pwd_nvme)
>>  			goto fail_clear_attr;
>>
>> +		/* Set default hdd/nvme index to 1 as there is no device 0 */
>> +		tlmi_priv.pwd_hdd->index = 1;
>> +		tlmi_priv.pwd_nvme->index = 1;
>> +
>>  		if (tlmi_priv.pwdcfg.core.password_state & TLMI_HDD_PWD) {
>>  			/* Check if PWD is configured and set index to first drive found */
>>  			if (tlmi_priv.pwdcfg.ext.hdd_user_password ||
>> -- 
>> 2.40.1
> 


  reply	other threads:[~2023-05-25 19:46 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 [this message]
2023-05-25 19:45       ` Mark Pearson
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=e5c4c61c-a3a3-97d0-ad50-8c5b345dc334@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@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

all inboxes | Powered by JetHome®