Linux Input/HID development
 help / color / mirror / Atom feed
From: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
To: Jiri Kosina <jkosina@suse.com>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: benjamin.tissoires@redhat.com, hdegoede@redhat.com,
	ilpo.jarvinen@linux.intel.com, mario.limonciello@amd.com,
	linux-input@vger.kernel.org, Patil Rajesh <Patil.Reddy@amd.com>
Subject: Re: [PATCH 0/3] Add new SFH interfaces
Date: Thu, 4 Jan 2024 13:59:45 +0530	[thread overview]
Message-ID: <71296fab-d6dd-490b-b29d-468f0eecb244@amd.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2401021122350.29548@cbobk.fhfr.pm>

Hi Jiri,

On 1/2/2024 3:53 PM, Jiri Kosina wrote:
> On Wed, 20 Dec 2023, Basavaraj Natikar wrote:
> 
>> This series adds new interfaces to export User presence information and
>> Ambient light to other drivers within the kernel.
> 
> Hi,
> 
> thanks for the patches. I'd like this to go in together with the actual 
> users of it on the PMF side. Does that code already exist?

I am yet to submit the patches that uses the new SFH interfaces
defined in this series.

The suggestion from Hans is to have the SFH changes landed
independently, so that Hans can take the PMF changes alone later
during the rc's as fix. IMO, we can have this series merged first alone.

But I am OK to have both PMF and SFH changes together.

Hans, what is your feedback for Jiri's question?

Thanks,
Shyam


> 
> Thanks,
> 

  reply	other threads:[~2024-01-04  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20  7:00 [PATCH 0/3] Add new SFH interfaces Basavaraj Natikar
2023-12-20  7:00 ` [PATCH 1/3] HID: amd_sfh: rename float_to_int() to amd_sfh_float_to_int() Basavaraj Natikar
2023-12-20  7:00 ` [PATCH 2/3] HID: amd_sfh: Add a new interface for exporting HPD data Basavaraj Natikar
2023-12-20  7:00 ` [PATCH 3/3] HID: amd_sfh: Add a new interface for exporting ALS data Basavaraj Natikar
2024-01-02 10:23 ` [PATCH 0/3] Add new SFH interfaces Jiri Kosina
2024-01-04  8:29   ` Shyam Sundar S K [this message]
2024-01-04  9:21     ` Hans de Goede
2024-01-04 14:20       ` 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=71296fab-d6dd-490b-b29d-468f0eecb244@amd.com \
    --to=shyam-sundar.s-k@amd.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=Patil.Reddy@amd.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jkosina@suse.com \
    --cc=linux-input@vger.kernel.org \
    --cc=mario.limonciello@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