From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
linux-sh@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 1/2] media: arch: sh: ecovec: Remove calls to empty arch_setup_pdev_archdata()
Date: Fri, 18 May 2018 13:06:50 +0200 [thread overview]
Message-ID: <1526641611-2769-2-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1526641611-2769-1-git-send-email-geert+renesas@glider.be>
SuperH doesn't implement arch_setup_pdev_archdata(), and falls back to
the default (empty) implementation. As this code is board-specific, the
calls can just be removed.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
arch/sh/boards/mach-ecovec24/setup.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/sh/boards/mach-ecovec24/setup.c b/arch/sh/boards/mach-ecovec24/setup.c
index adc61d14172c63b8..dc9708227b0d58e8 100644
--- a/arch/sh/boards/mach-ecovec24/setup.c
+++ b/arch/sh/boards/mach-ecovec24/setup.c
@@ -1396,7 +1396,6 @@ static int __init arch_setup(void)
/* Initialize CEU platform devices separately to map memory first */
device_initialize(&ecovec_ceu_devices[0]->dev);
- arch_setup_pdev_archdata(ecovec_ceu_devices[0]);
dma_declare_coherent_memory(&ecovec_ceu_devices[0]->dev,
ceu0_dma_membase, ceu0_dma_membase,
ceu0_dma_membase +
@@ -1405,7 +1404,6 @@ static int __init arch_setup(void)
platform_device_add(ecovec_ceu_devices[0]);
device_initialize(&ecovec_ceu_devices[1]->dev);
- arch_setup_pdev_archdata(ecovec_ceu_devices[1]);
dma_declare_coherent_memory(&ecovec_ceu_devices[1]->dev,
ceu1_dma_membase, ceu1_dma_membase,
ceu1_dma_membase +
--
2.7.4
next prev parent reply other threads:[~2018-05-18 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 11:06 [PATCH 0/2] Remove calls to empty arch_setup_pdev_archdata() Geert Uytterhoeven
2018-05-18 11:06 ` Geert Uytterhoeven [this message]
2018-05-22 8:22 ` [PATCH 1/2] media: arch: sh: ecovec: " Simon Horman
2018-05-18 11:06 ` [PATCH 2/2] media: arch: sh: migor: " Geert Uytterhoeven
2018-05-22 8:22 ` Simon Horman
2018-05-18 11:52 ` [PATCH 0/2] " jacopo mondi
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=1526641611-2769-2-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=dalias@libc.org \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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).