From: Dmitry Osipenko <digetx@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Joseph Lo <josephl@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 04/13] memory: tegra20-emc: Include io.h instead of iopoll.h
Date: Mon, 8 Jul 2019 01:54:15 +0300 [thread overview]
Message-ID: <20190707225424.9562-5-digetx@gmail.com> (raw)
In-Reply-To: <20190707225424.9562-1-digetx@gmail.com>
The register polling code was gone, but the included header change was
missed. Fix it up for consistency.
Acked-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
drivers/memory/tegra/tegra20-emc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/memory/tegra/tegra20-emc.c b/drivers/memory/tegra/tegra20-emc.c
index b519f02b0ee9..1ce351dd5461 100644
--- a/drivers/memory/tegra/tegra20-emc.c
+++ b/drivers/memory/tegra/tegra20-emc.c
@@ -10,7 +10,7 @@
#include <linux/completion.h>
#include <linux/err.h>
#include <linux/interrupt.h>
-#include <linux/iopoll.h>
+#include <linux/io.h>
#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/of.h>
--
2.22.0
next prev parent reply other threads:[~2019-07-07 22:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 22:54 [PATCH v7 00/13] memory: tegra: Introduce Tegra30 EMC driver Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 01/13] clk: tegra20/30: Add custom EMC clock implementation Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 02/13] memory: tegra20-emc: Drop setting EMC rate to max on probe Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 03/13] memory: tegra20-emc: Adapt for clock driver changes Dmitry Osipenko
2019-07-07 22:54 ` Dmitry Osipenko [this message]
2019-07-07 22:54 ` [PATCH v7 05/13] memory: tegra20-emc: Pre-configure debug register Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 06/13] memory: tegra20-emc: Print a brief info message about the timings Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 07/13] dt-bindings: memory: tegra30: Convert to Tegra124 YAML Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 08/13] dt-bindings: memory: Add binding for NVIDIA Tegra30 Memory Controller Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 09/13] dt-bindings: memory: Add binding for NVIDIA Tegra30 External " Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 10/13] memory: tegra: Introduce Tegra30 EMC driver Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 11/13] memory: tegra: Ensure timing control debug features are disabled Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 12/13] memory: tegra: Consolidate registers definition into common header Dmitry Osipenko
2019-07-07 22:54 ` [PATCH v7 13/13] ARM: dts: tegra30: Add External Memory Controller node Dmitry Osipenko
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=20190707225424.9562-5-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--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=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).