From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: Darren Hart <dvhart@infradead.org>,
"Chakravarty, Souvik K" <souvik.k.chakravarty@intel.com>
Cc: "Zha, Qipeng" <qipeng.zha@intel.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform:x86 decouple telemetry driver from the optional IPC resources
Date: Mon, 11 Apr 2016 15:05:50 +0800 [thread overview]
Message-ID: <570B4CCE.7030501@linux.intel.com> (raw)
In-Reply-To: <20160411064821.GA14283@dvhart-mobl5.amr.corp.intel.com>
On 2016/4/11 14:48, Darren Hart wrote:
> On Mon, Apr 11, 2016 at 04:04:55AM +0000, Chakravarty, Souvik K wrote:
>>
>>
>>> -----Original Message-----
>>> From: Zha, Qipeng
>>> Sent: Monday, April 11, 2016 7:34 AM
>>> To: Darren Hart <dvhart@infradead.org>; Aubrey Li
>>> <aubrey.li@linux.intel.com>; Chakravarty, Souvik K
>>> <souvik.k.chakravarty@intel.com>
>>> Cc: platform-driver-x86@vger.kernel.org; linux-kernel@vger.kernel.org
>>> Subject: RE: [PATCH] platform:x86 decouple telemetry driver from the
>>> optional IPC resources
>>>
>>>>> Currently the optional IPC resources prevent telemetry driver from
>>>>> probing if these resources are not in ACPI table. This patch
>>>>> decouples telemetry driver from these optional resources, so that
>>>>> telemetry driver has dependency only on the necessary ACPI resources.
>>>>>
>>>>> Signed-off-by: Aubrey Li <aubrey.li@linux.intel.com>
>>>
>>>> Given the impact to their recent contributions, I'm looking for reviews from
>>> Qipeng and Souvik before I merge this.
>>>
>>>> Qipeng, as the listed maintainer for these two files, I particularly need to
>>> hear from you.
>>>
>>>> Thanks,
>>>
>>> Hi Darren, I think this is a reasonable solution for such issue.
>>> Thanks Aubrey for this fixing patch.
>>
>> We went over this internally once. So OK from my POV.
>
> Qipeng and Souvik, I appreciate the responses.
Thank you all. -Aubrey
>
> As a point of process, I won't include a "Reviewed-by:" unless you explicitly
> include it in your response.
>
next prev parent reply other threads:[~2016-04-11 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 19:28 [PATCH] platform:x86 decouple telemetry driver from the optional IPC resources Aubrey Li
2016-04-10 2:45 ` Darren Hart
2016-04-11 2:04 ` Zha, Qipeng
2016-04-11 4:04 ` Chakravarty, Souvik K
2016-04-11 6:48 ` Darren Hart
2016-04-11 7:05 ` Li, Aubrey [this message]
2016-04-10 13:17 ` Andy Shevchenko
2016-04-10 13:46 ` Li, Aubrey
2016-04-15 0:32 ` Darren Hart
2016-04-15 2:18 ` Li, Aubrey
2016-04-15 5:05 ` Darren Hart
2016-04-21 21:13 ` Andy Shevchenko
2016-04-19 21:17 ` Darren Hart
2016-04-21 21:10 ` 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=570B4CCE.7030501@linux.intel.com \
--to=aubrey.li@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qipeng.zha@intel.com \
--cc=souvik.k.chakravarty@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.