From: Hiroshi DOYU <hdoyu@nvidia.com>
To: <hdoyu@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Warren <swarren@wwwdotorg.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 1/1] memory: tegra{20,30}-mc: Remove empty *_remove()
Date: Mon, 14 May 2012 19:20:03 +0300 [thread overview]
Message-ID: <1337012410-19067-1-git-send-email-hdoyu@nvidia.com> (raw)
Remove unnecessary empty functions.
Signed-off-by: Hiroshi DOYU <hdoyu@nvidia.com>
---
drivers/memory/tegra20-mc.c | 6 ------
drivers/memory/tegra30-mc.c | 6 ------
2 files changed, 0 insertions(+), 12 deletions(-)
diff --git a/drivers/memory/tegra20-mc.c b/drivers/memory/tegra20-mc.c
index a38d9d3..3ed49c1 100644
--- a/drivers/memory/tegra20-mc.c
+++ b/drivers/memory/tegra20-mc.c
@@ -241,14 +241,8 @@ static int __devinit tegra20_mc_probe(struct platform_device *pdev)
return 0;
}
-static int __devexit tegra20_mc_remove(struct platform_device *pdev)
-{
- return 0;
-}
-
static struct platform_driver tegra20_mc_driver = {
.probe = tegra20_mc_probe,
- .remove = __devexit_p(tegra20_mc_remove),
.driver = {
.name = DRV_NAME,
.owner = THIS_MODULE,
diff --git a/drivers/memory/tegra30-mc.c b/drivers/memory/tegra30-mc.c
index cb639b1..e56ff04 100644
--- a/drivers/memory/tegra30-mc.c
+++ b/drivers/memory/tegra30-mc.c
@@ -365,14 +365,8 @@ static int __devinit tegra30_mc_probe(struct platform_device *pdev)
return 0;
}
-static int __devexit tegra30_mc_remove(struct platform_device *pdev)
-{
- return 0;
-}
-
static struct platform_driver tegra30_mc_driver = {
.probe = tegra30_mc_probe,
- .remove = __devexit_p(tegra30_mc_remove),
.driver = {
.name = DRV_NAME,
.owner = THIS_MODULE,
--
1.7.5.4
reply other threads:[~2012-05-14 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1337012410-19067-1-git-send-email-hdoyu@nvidia.com \
--to=hdoyu@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®