From: Stephen Boyd <sboyd@kernel.org>
To: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>, linux-clk@vger.kernel.org
Cc: Vijendar.Mukunda@amd.com, Alexander.Deucher@amd.com,
Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
Mario.Limonciello@amd.com,
Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>,
Michael Turquette <mturquette@baylibre.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 4/5] clk: x86: Use dynamic con_id string during clk registration
Date: Thu, 06 Jan 2022 17:59:16 -0800 [thread overview]
Message-ID: <20220107015917.480F0C36AE0@smtp.kernel.org> (raw)
In-Reply-To: <20211212180527.1641362-5-AjitKumar.Pandey@amd.com>
Quoting Ajit Kumar Pandey (2021-12-12 10:05:26)
> Replace hard coded con_id string with fch_data->name. We have clk
> consumers looking up with different clock names, hence use dynamic
> con_id string during clk lookup registration. fch_data->name will
> be initialized in acpi driver based on fmw property value.
>
> Signed-off-by: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
> Reviewed-by: Mario Limonciello <Mario.Limonciello@amd.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2022-01-07 1:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 18:05 [PATCH v5 0/5] clk-fch: Add support for newer family of AMD's SOC Ajit Kumar Pandey
2021-12-12 18:05 ` [PATCH v5 1/5] x86: clk: " Ajit Kumar Pandey
2022-01-07 1:58 ` Stephen Boyd
2021-12-12 18:05 ` [PATCH v5 2/5] drivers: acpi: acpi_apd: Remove unused device property "is-rv" Ajit Kumar Pandey
2021-12-17 18:06 ` Rafael J. Wysocki
2021-12-17 18:19 ` Limonciello, Mario
2021-12-17 18:23 ` Rafael J. Wysocki
2021-12-12 18:05 ` [PATCH v5 3/5] ACPI: APD: Add a fmw property clk-name Ajit Kumar Pandey
2021-12-12 18:05 ` [PATCH v5 4/5] clk: x86: Use dynamic con_id string during clk registration Ajit Kumar Pandey
2022-01-07 1:59 ` Stephen Boyd [this message]
2021-12-12 18:05 ` [PATCH v5 5/5] clk: x86: Fix clk_gate_flags for RV_CLK_GATE Ajit Kumar Pandey
2022-01-07 1:59 ` Stephen Boyd
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=20220107015917.480F0C36AE0@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=AjitKumar.Pandey@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.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.