From: Thierry Reding <thierry.reding@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Joseph Lo <josephl@nvidia.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] memory: tegra: Drop <linux/clk-provider.h>
Date: Thu, 7 May 2020 22:04:10 +0200 [thread overview]
Message-ID: <20200507200410.GB2981633@ulmo> (raw)
In-Reply-To: <20200506123236.7463-3-geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Wed, May 06, 2020 at 02:32:36PM +0200, Geert Uytterhoeven wrote:
> The Tegra EMC scaling support code is not a clock provider, but merely a
> clock consumer, and thus does not need to include
> <linux/clk-provider.h>.
>
> Fixes: ec37a9a17afbfad5 ("memory: tegra: Add EMC scaling support code for Tegra210")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/memory/tegra/tegra210-emc-core.c | 1 -
> drivers/memory/tegra/tegra210-emc.h | 1 -
> 2 files changed, 2 deletions(-)
Applied to for-5.8/memory, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-07 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 12:32 [PATCH 0/2] memory: tegra: EMC scaling is not a clock provider Geert Uytterhoeven
2020-05-06 12:32 ` [PATCH 1/2] of: Make <linux/of_reserved_mem.h> self-contained Geert Uytterhoeven
2020-05-07 20:04 ` Thierry Reding
2020-05-12 21:15 ` Stephen Boyd
2020-05-06 12:32 ` [PATCH 2/2] memory: tegra: Drop <linux/clk-provider.h> Geert Uytterhoeven
2020-05-07 20:04 ` Thierry Reding [this message]
2020-06-15 8:39 ` Geert Uytterhoeven
2020-05-12 21:15 ` Stephen Boyd
2020-05-07 20:07 ` [PATCH 0/2] memory: tegra: EMC scaling is not a clock provider Thierry Reding
2020-05-11 17:17 ` Rob Herring
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=20200507200410.GB2981633@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=jonathanh@nvidia.com \
--cc=josephl@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@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).