From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Xue, Ken" <Ken.Xue@amd.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"mika.wasterberg@linux.intel.com"
<mika.wasterberg@linux.intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wu, Jeff" <Jeff.Wu@amd.com>
Subject: Re: [PATCH] acpi:apd:add AMD ACPI2Platform device support for x86 system.
Date: Fri, 21 Nov 2014 15:58:41 +0100 [thread overview]
Message-ID: <4186825.AlJiqLqNxs@vostro.rjw.lan> (raw)
In-Reply-To: <4AC89B18A26BAB43B540DB1C94E2802C05A47EDE@scybexdag03.amd.com>
On Friday, November 21, 2014 05:15:46 AM Xue, Ken wrote:
> Hi Len, Rafael J & Mika,
> Please help to review this patch. And tell me any of your concern. Thanks.
>
> I understand it is a trend that convert a ACPI device to be a platform device.
> For AMD, we try to use this patch to match this trend well. The patch based on INTEL LPSS .
> But we cannot reuse LPSS, because of specific definition of "lpss_device_desc" for LPSS.
You don't have to resend the patch every day for us to notice it. We're
actually in the process of reviewing your original submission.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-11-21 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 5:58 [PATCH] acpi:apd:add AMD ACPI2Platform device support for x86 system Ken Xue
2014-11-21 5:15 ` Xue, Ken
2014-11-21 14:58 ` Rafael J. Wysocki [this message]
2014-11-24 1:15 ` Rafael J. Wysocki
2014-11-24 1:02 ` Xue, Ken
2014-11-24 1:47 ` Rafael J. Wysocki
2014-11-26 10:31 ` Ken Xue
2014-11-27 11:46 ` Mika Westerberg
2014-11-27 17:06 ` Rafael J. Wysocki
2014-11-27 16:48 ` Mika Westerberg
2014-11-28 1:33 ` Ken Xue
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=4186825.AlJiqLqNxs@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=Jeff.Wu@amd.com \
--cc=Ken.Xue@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.wasterberg@linux.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