From: trix@redhat.com
To: mdf@kernel.org
Cc: linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
Tom Rix <trix@redhat.com>
Subject: [PATCH] fpga: remove empty release functions
Date: Wed, 19 May 2021 07:58:44 -0700 [thread overview]
Message-ID: <20210519145844.1962294-1-trix@redhat.com> (raw)
From: Tom Rix <trix@redhat.com>
Unneeded functions, so remove.
Signed-off-by: Tom Rix <trix@redhat.com>
---
drivers/fpga/fpga-bridge.c | 5 -----
drivers/fpga/fpga-mgr.c | 5 -----
drivers/fpga/fpga-region.c | 5 -----
3 files changed, 15 deletions(-)
diff --git a/drivers/fpga/fpga-bridge.c b/drivers/fpga/fpga-bridge.c
index e9266b2a357f6..6510c7803a784 100644
--- a/drivers/fpga/fpga-bridge.c
+++ b/drivers/fpga/fpga-bridge.c
@@ -473,10 +473,6 @@ void fpga_bridge_unregister(struct fpga_bridge *bridge)
}
EXPORT_SYMBOL_GPL(fpga_bridge_unregister);
-static void fpga_bridge_dev_release(struct device *dev)
-{
-}
-
static int __init fpga_bridge_dev_init(void)
{
fpga_bridge_class = class_create(THIS_MODULE, "fpga_bridge");
@@ -484,7 +480,6 @@ static int __init fpga_bridge_dev_init(void)
return PTR_ERR(fpga_bridge_class);
fpga_bridge_class->dev_groups = fpga_bridge_groups;
- fpga_bridge_class->dev_release = fpga_bridge_dev_release;
return 0;
}
diff --git a/drivers/fpga/fpga-mgr.c b/drivers/fpga/fpga-mgr.c
index b85bc47c91a9a..e0e1835beab77 100644
--- a/drivers/fpga/fpga-mgr.c
+++ b/drivers/fpga/fpga-mgr.c
@@ -779,10 +779,6 @@ int devm_fpga_mgr_register(struct device *dev, struct fpga_manager *mgr)
}
EXPORT_SYMBOL_GPL(devm_fpga_mgr_register);
-static void fpga_mgr_dev_release(struct device *dev)
-{
-}
-
static int __init fpga_mgr_class_init(void)
{
pr_info("FPGA manager framework\n");
@@ -792,7 +788,6 @@ static int __init fpga_mgr_class_init(void)
return PTR_ERR(fpga_mgr_class);
fpga_mgr_class->dev_groups = fpga_mgr_groups;
- fpga_mgr_class->dev_release = fpga_mgr_dev_release;
return 0;
}
diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c
index c3134b89c3fe5..ddaca70b21de5 100644
--- a/drivers/fpga/fpga-region.c
+++ b/drivers/fpga/fpga-region.c
@@ -314,10 +314,6 @@ void fpga_region_unregister(struct fpga_region *region)
}
EXPORT_SYMBOL_GPL(fpga_region_unregister);
-static void fpga_region_dev_release(struct device *dev)
-{
-}
-
/**
* fpga_region_init - init function for fpga_region class
* Creates the fpga_region class and registers a reconfig notifier.
@@ -329,7 +325,6 @@ static int __init fpga_region_init(void)
return PTR_ERR(fpga_region_class);
fpga_region_class->dev_groups = fpga_region_groups;
- fpga_region_class->dev_release = fpga_region_dev_release;
return 0;
}
--
2.26.3
reply other threads:[~2021-05-19 14:58 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=20210519145844.1962294-1-trix@redhat.com \
--to=trix@redhat.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@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