mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Hans de Goede" <hdegoede@redhat.com>
Cc: "markgross@kernel.org" <markgross@kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: think-lmi: Add bulk save feature
Date: Thu, 21 Sep 2023 13:43:36 -0400	[thread overview]
Message-ID: <a94579f0-8d4a-48c5-9ecb-1fc5de7a6849@app.fastmail.com> (raw)
In-Reply-To: <e29cd141-0f38-e806-51cb-bc82c451b9c4@redhat.com>


On Thu, Sep 21, 2023, at 12:38 PM, Hans de Goede wrote:
> Hi Mark,
>
> On 9/19/23 16:15, Mark Pearson wrote:
>> On Lenovo platforms there is a limitation in the number of times an
>> attribute can be saved. This is an architectural limitation and it limits
>> the number of attributes that can be modified to 48.
>> A solution for this is instead of the attribute being saved after every
>> modification allow a user to bulk set the attributes and then trigger a
>> final save. This allows unlimited attributes.
>> 
>> This patch introduces a save_settings attribute that can be configured to
>> either single or bulk mode by the user.
>> Single mode is the default but customers who want to avoid the 48
>> attribute limit can enable bulk mode.
>> 
>> Displaying the save_settings attribute will display the enabled mode.
>> 
>> When in bulk mode writing 'save' to the save_settings attribute will
>> trigger a save. Once this has been done a reboot is required before more
>> attributes can be modified.
>> 
>> Signed-off-by: Mark Pearson <mpearson-lenovo@squebb.ca>
>> ---
>> Changes in v2:
>>  - Correct kernel version in documentation
>>  - Updated to sysfs_emit
>>  - Clean up code in save_settings_store as recommended
>>  - Use correct comment formatting
>
> Thank you for the new version, but next time when a patch has
> already been merged please send any fixes as a follow-up /
> separate patch with just the fixes.
>
> I've replaced the original patch with this one now doing
> a forced push to both my review-hans and the for-next
> branch.
>
Oh - my apologies, I didn't think of that. Thanks for cleaning up for me.
Mark

  reply	other threads:[~2023-09-21 20:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 14:15 Mark Pearson
2023-09-21 16:38 ` Hans de Goede
2023-09-21 17:43   ` Mark Pearson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-06 12:13 Mark Pearson
2023-09-13 16:40 ` Hans de Goede
2023-09-18 13:57 ` Andy Shevchenko
2023-09-18 14:00   ` Andy Shevchenko
2023-09-18 16:25     ` Joe Perches
2023-09-18 14:07   ` Hans de Goede
2023-09-18 14:38     ` Andy Shevchenko
2023-09-18 16:22       ` Joe Perches
2023-09-18 14:39     ` Andy Shevchenko
2023-09-18 15:23     ` Mark Pearson
2023-09-19  8:32       ` 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=a94579f0-8d4a-48c5-9ecb-1fc5de7a6849@app.fastmail.com \
    --to=mpearson-lenovo@squebb.ca \
    --cc=andriy.shevchenko@intel.com \
    --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®