From: "Agrawal, Akshu" <aagrawal2@amd.com>
To: Stephen Boyd <sboyd@kernel.org>, akshu.agrawal@amd.com
Cc: rafael@kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [v2 1/4] ACPI: APD: Change name from ST to FCH
Date: Fri, 31 Jul 2020 06:14:10 +0530 [thread overview]
Message-ID: <c5041407-1bbb-82b3-e5a5-c6de0ab16861@amd.com> (raw)
In-Reply-To: <159598596077.1360974.483730969007254506@swboyd.mtv.corp.google.com>
On 7/29/2020 6:56 AM, Stephen Boyd wrote:
> Quoting Akshu Agrawal (2020-07-28 01:28:53)
>> AMD SoC general pupose clk is present in new platforms with
>> same MMIO mappings. We can reuse the same clk handler support
>> for other platforms. Hence, changing name from ST(SoC) to FCH(IP)
>>
>> Signed-off-by: Akshu Agrawal <akshu.agrawal@amd.com>
>> ---
> Acked-by: Stephen Boyd <sboyd@kernel.org>
Hi Rafael,
I see the status of these patches as Not Applicable in patchwork, is
there any pending action for me?
Thanks,
Akshu
next prev parent reply other threads:[~2020-07-31 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200728082857.10829-1-akshu.agrawal@amd.com>
2020-07-28 8:28 ` [v2 1/4] ACPI: APD: Change name from ST to FCH Akshu Agrawal
[not found] ` <159598596077.1360974.483730969007254506@swboyd.mtv.corp.google.com>
2020-07-31 0:44 ` Agrawal, Akshu [this message]
2020-07-31 11:14 ` Rafael J. Wysocki
2020-07-31 13:33 ` Agrawal, Akshu
2020-07-28 8:28 ` [v2 2/4] clk: x86: " Akshu Agrawal
2020-07-29 1:25 ` Stephen Boyd
2020-07-28 8:28 ` [v3 4/4] clk: x86: Support RV architecture Akshu Agrawal
2020-07-29 1:26 ` Stephen Boyd
2020-07-31 13:36 [0/4] Extend AMD SoC general purpose clk for all versions Akshu Agrawal
2020-07-31 13:36 ` [v2 1/4] ACPI: APD: Change name from ST to FCH Akshu Agrawal
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=c5041407-1bbb-82b3-e5a5-c6de0ab16861@amd.com \
--to=aagrawal2@amd.com \
--cc=akshu.agrawal@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
/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).