From: Basavaraj Natikar <bnatikar@amd.com>
To: Mario Limonciello <superm1@kernel.org>,
Basavaraj Natikar <basavaraj.natikar@amd.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>
Cc: open list <linux-kernel@vger.kernel.org>,
"open list:AMD SENSOR FUSION HUB DRIVER"
<linux-input@vger.kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH v4 RESEND 0/2] Fixes for SRA sensor handling
Date: Tue, 22 Apr 2025 09:55:00 +0530 [thread overview]
Message-ID: <3055e872-176b-4189-a735-aa9caebc207f@amd.com> (raw)
In-Reply-To: <20250421213210.1160665-1-superm1@kernel.org>
On 4/22/2025 3:02 AM, Mario Limonciello wrote:
> From: Mario Limonciello <mario.limonciello@amd.com>
>
> On systems with an SRA sensor there are some problems with both init
> and failure paths. This series accounts for both.
>
> This is resend of V4 which ahsn't gotten any movement the past two
> weeks:
> Link: https://patchwork.kernel.org/project/linux-input/cover/20250407151835.1200867-1-superm1@kernel.org/
>
> Mario Limonciello (2):
> HID: amd_sfh: Fix SRA sensor when it's the only sensor
> HID: amd_sfh: Avoid clearing reports for SRA sensor
>
> drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_init.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
Looks good to me.
Acked-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Thanks,
--
Basavaraj
next prev parent reply other threads:[~2025-04-22 4:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 21:32 [PATCH v4 RESEND 0/2] Fixes for SRA sensor handling Mario Limonciello
2025-04-21 21:32 ` [PATCH v4 RESEND 1/2] HID: amd_sfh: Fix SRA sensor when it's the only sensor Mario Limonciello
2025-04-21 21:32 ` [PATCH v4 RESEND 2/2] HID: amd_sfh: Avoid clearing reports for SRA sensor Mario Limonciello
2025-04-22 4:25 ` Basavaraj Natikar [this message]
2025-04-24 10:18 ` [PATCH v4 RESEND 0/2] Fixes for SRA sensor handling Jiri Kosina
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=3055e872-176b-4189-a735-aa9caebc207f@amd.com \
--to=bnatikar@amd.com \
--cc=basavaraj.natikar@amd.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=superm1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.