linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Gayatri Kammela <gayatri.kammela@intel.com>
Cc: linux-pm@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	alex.hung@canonical.com, linux-acpi@vger.kernel.org,
	lenb@kernel.org, rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
	daniel.lezcano@linaro.org, amit.kucheria@verdurent.com,
	charles.d.prestopine@intel.com, dvhart@infradead.org,
	Zhang Rui <rui.zhang@intel.com>,
	Srinivas Pandruvada <srinivas.pandruvada@intel.com>
Subject: Re: [PATCH v2 3/4] platform/x86: intel-hid: Add new Tiger Lake hardware ID to support HID driver
Date: Mon, 16 Dec 2019 14:13:20 +0200	[thread overview]
Message-ID: <20191216121320.GQ32742@smile.fi.intel.com> (raw)
In-Reply-To: <a70a856e9a87c89ba92da514c1dda1f46f10b0de.1576260216.git.gayatri.kammela@intel.com>

On Fri, Dec 13, 2019 at 10:14:22AM -0800, Gayatri Kammela wrote:
> Tiger Lake has a new unique hardware ID to support Intel's HID event
> filter driver. Hence, add it.
> 

Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

> Cc: Zhang Rui <rui.zhang@intel.com>
> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Srinivas Pandruvada <srinivas.pandruvada@intel.com>
> Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
> ---
>  drivers/platform/x86/intel-hid.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/platform/x86/intel-hid.c b/drivers/platform/x86/intel-hid.c
> index ef6d4bd77b1a..43d590250228 100644
> --- a/drivers/platform/x86/intel-hid.c
> +++ b/drivers/platform/x86/intel-hid.c
> @@ -19,6 +19,7 @@ MODULE_LICENSE("GPL");
>  MODULE_AUTHOR("Alex Hung");
>  
>  static const struct acpi_device_id intel_hid_ids[] = {
> +	{"INT1051", 0},
>  	{"INT33D5", 0},
>  	{"", 0},
>  };
> -- 
> 2.17.1
> 

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2019-12-16 12:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 18:14 [PATCH v2 0/4] drivers: Add Tiger Lake hardware IDs to support acpi, Gayatri Kammela
2019-12-13 18:14 ` [PATCH v2 1/4] acpi: dptf: Add new Tiger Lake hardware IDs to support DPTF drivers in acpi Gayatri Kammela
2019-12-13 18:14 ` [PATCH v2 2/4] acpi: fan: Add new Tiger Lake hardware ID to support fan driver " Gayatri Kammela
2019-12-16  8:58   ` Rafael J. Wysocki
2019-12-16 17:13     ` Kammela, Gayatri
2019-12-13 18:14 ` [PATCH v2 3/4] platform/x86: intel-hid: Add new Tiger Lake hardware ID to support HID driver Gayatri Kammela
2019-12-16 12:13   ` Andy Shevchenko [this message]
2019-12-16 17:15     ` Kammela, Gayatri
2019-12-13 18:14 ` [PATCH v2 4/4] thermal: int340x_thermal: Add new Tiger Lake hardware IDs to support thermal driver Gayatri Kammela
2019-12-16 17:05   ` Pandruvada, Srinivas
2019-12-16 17:15     ` Kammela, Gayatri

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=20191216121320.GQ32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alex.hung@canonical.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=charles.d.prestopine@intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=dvhart@infradead.org \
    --cc=gayatri.kammela@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@intel.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 NNTP newsgroup(s).