From: Andrew Davis <afd@ti.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, "Andrew Davis" <afd@ti.com>
Subject: [PATCH 2/2] remoteproc: pru: Remove empty remove callback
Date: Mon, 2 Mar 2026 14:27:28 -0600 [thread overview]
Message-ID: <20260302202728.322073-2-afd@ti.com> (raw)
In-Reply-To: <20260302202728.322073-1-afd@ti.com>
The .remove() callback only prints out a debug message, remove
this otherwise unneeded callback.
Signed-off-by: Andrew Davis <afd@ti.com>
---
drivers/remoteproc/pru_rproc.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
index 19b107d29242d..a4636c7bc6b7b 100644
--- a/drivers/remoteproc/pru_rproc.c
+++ b/drivers/remoteproc/pru_rproc.c
@@ -1078,14 +1078,6 @@ static int pru_rproc_probe(struct platform_device *pdev)
return 0;
}
-static void pru_rproc_remove(struct platform_device *pdev)
-{
- struct device *dev = &pdev->dev;
- struct rproc *rproc = platform_get_drvdata(pdev);
-
- dev_dbg(dev, "%s: removing rproc %s\n", __func__, rproc->name);
-}
-
static const struct pru_private_data pru_data = {
.type = PRU_TYPE_PRU,
};
@@ -1131,7 +1123,6 @@ static struct platform_driver pru_rproc_driver = {
.suppress_bind_attrs = true,
},
.probe = pru_rproc_probe,
- .remove = pru_rproc_remove,
};
module_platform_driver(pru_rproc_driver);
--
2.39.2
next prev parent reply other threads:[~2026-03-02 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 20:27 [PATCH 1/2] remoteproc: pru: Use rproc_of_parse_firmware() to get firmware name Andrew Davis
2026-03-02 20:27 ` Andrew Davis [this message]
2026-03-06 17:35 ` Mathieu Poirier
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=20260302202728.322073-2-afd@ti.com \
--to=afd@ti.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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®