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 v1 2/4] acpi: fan: Add new Tiger Lake hardware ID to support fan driver in acpi
Date: Fri, 13 Dec 2019 11:35:01 +0200 [thread overview]
Message-ID: <20191213093501.GP32742@smile.fi.intel.com> (raw)
In-Reply-To: <68c6a37a5fcce792de61c4a0adcce0b83694e8d0.1576189376.git.gayatri.kammela@intel.com>
On Thu, Dec 12, 2019 at 02:37:18PM -0800, Gayatri Kammela wrote:
> {"PNP0C0B", 0},
> {"INT3404", 0},
> + {"INT1044", 0},
Same comment here.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-12-13 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 22:37 [PATCH v1 0/4] drivers: Add Tiger Lake hardware IDs to support acpi, Gayatri Kammela
2019-12-12 22:37 ` [PATCH v1 1/4] acpi: dptf: Add new Tiger Lake hardware IDs to support DPTF drivers in acpi Gayatri Kammela
2019-12-13 9:34 ` Andy Shevchenko
2019-12-13 17:54 ` Kammela, Gayatri
2019-12-12 22:37 ` [PATCH v1 2/4] acpi: fan: Add new Tiger Lake hardware ID to support fan driver " Gayatri Kammela
2019-12-13 9:35 ` Andy Shevchenko [this message]
2019-12-12 22:37 ` [PATCH v1 3/4] platform/x86: intel-hid: Add new Tiger Lake hardware ID to support HID driver Gayatri Kammela
2019-12-13 9:35 ` Andy Shevchenko
2019-12-12 22:37 ` [PATCH v1 4/4] thermal: int340x_thermal: Add new Tiger Lake hardware IDs to support thermal driver Gayatri Kammela
2019-12-13 9:35 ` Andy Shevchenko
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=20191213093501.GP32742@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 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.