From: Armin Wolf <W_Armin@gmx.de>
To: Joshua Grisham <josh@joshuagrisham.com>,
thomas@t-8ch.de, kuurtb@gmail.com, ilpo.jarvinen@linux.intel.com,
hdegoede@redhat.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: samsung-galaxybook: Fix block_recording not supported logic
Date: Wed, 5 Mar 2025 01:29:24 +0100 [thread overview]
Message-ID: <3f779992-1a3b-475b-b07b-3a4ca02f5b35@gmx.de> (raw)
In-Reply-To: <20250303132433.348653-1-josh@joshuagrisham.com>
Am 03.03.25 um 14:24 schrieb Joshua Grisham:
> Fixes logic error when block_recording is not supported but the fw attr was
> being added anyway (reported by GitHub user bbregeault).
>
> Tested myself on a Samsung Galaxy Book2 Pro (has block_recording) and by
> bbregeault on a Galaxy Book2 Business (does not have block_recording).
For the future you can use Tested-by tags to indicate who tested this patch.
For now:
Reviewed-by: Armin Wolf <W_Armin@gmx.de>
> Fixes: 56f529ce4370 ("platform/x86: samsung-galaxybook: Add samsung-galaxybook driver")
>
> Signed-off-by: Joshua Grisham <josh@joshuagrisham.com>
>
> ---
> v1->v2:
> - Add Fixes tag with prior commit (thanks Ilpo for catching!)
> ---
> drivers/platform/x86/samsung-galaxybook.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/platform/x86/samsung-galaxybook.c b/drivers/platform/x86/samsung-galaxybook.c
> index de1ed2dc6..5878a3519 100644
> --- a/drivers/platform/x86/samsung-galaxybook.c
> +++ b/drivers/platform/x86/samsung-galaxybook.c
> @@ -1100,11 +1100,13 @@ static int galaxybook_fw_attrs_init(struct samsung_galaxybook *galaxybook)
> }
>
> err = galaxybook_block_recording_init(galaxybook);
> - if (!err)
> - galaxybook->has_block_recording = true;
> - else if (err != GB_NOT_SUPPORTED)
> + if (err == GB_NOT_SUPPORTED)
> + return 0;
> + else if (err)
> return err;
>
> + galaxybook->has_block_recording = true;
> +
> return galaxybook_fw_attr_init(galaxybook,
> GB_ATTR_BLOCK_RECORDING,
> &block_recording_acpi_get,
next prev parent reply other threads:[~2025-03-05 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 13:24 Joshua Grisham
2025-03-05 0:29 ` Armin Wolf [this message]
2025-03-05 13:09 ` Ilpo Järvinen
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=3f779992-1a3b-475b-b07b-3a4ca02f5b35@gmx.de \
--to=w_armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=josh@joshuagrisham.com \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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®