Linux Input Archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: benjamin.tissoires@redhat.com, linux-input@vger.kernel.org,
	 patreddy@amd.com
Subject: Re: [PATCH 0/3] Fixes and updates to amd-sfh
Date: Tue, 7 May 2024 15:19:12 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2405071519040.16865@cbobk.fhfr.pm> (raw)
In-Reply-To: <20240507071045.295723-1-Basavaraj.Natikar@amd.com>

On Tue, 7 May 2024, Basavaraj Natikar wrote:

> This patch series include changes for:
> - Modify and log errors based on functionality.
> - Handle "no sensors" exists in PM operations.
> - Use amd_get_c2p_val() to read the C2P register for compatibility.
> 
> Basavaraj Natikar (3):
>   HID: amd_sfh: Modify and log error only if case of functionality
>     failures
>   HID: amd_sfh: Handle "no sensors" in PM operations
>   HID: amd_sfh: Use amd_get_c2p_val() to read C2P register
> 
>  drivers/hid/amd-sfh-hid/amd_sfh_pcie.c          |  5 +----
>  drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_init.c   | 17 ++++++++++++++---
>  .../hid/amd-sfh-hid/sfh1_1/amd_sfh_interface.c  |  2 +-
>  3 files changed, 16 insertions(+), 8 deletions(-)

Queued for 6.10, thanks.

-- 
Jiri Kosina
SUSE Labs


      parent reply	other threads:[~2024-05-07 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07  7:10 [PATCH 0/3] Fixes and updates to amd-sfh Basavaraj Natikar
2024-05-07  7:10 ` [PATCH 1/3] HID: amd_sfh: Modify and log error only if case of functionality failures Basavaraj Natikar
2024-05-07  7:10 ` [PATCH 2/3] HID: amd_sfh: Handle "no sensors" in PM operations Basavaraj Natikar
2024-05-07  7:10 ` [PATCH 3/3] HID: amd_sfh: Use amd_get_c2p_val() to read C2P register Basavaraj Natikar
2024-05-07 13:19 ` Jiri Kosina [this message]

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=nycvar.YFH.7.76.2405071519040.16865@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=patreddy@amd.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).