From: Sumit Gupta <sumitg@nvidia.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@pengutronix.de>, Sumit Gupta <sumitg@nvidia.com>
Subject: Re: [PATCH 3/3] soc: tegra: cbb: Drop empty platform remove function
Date: Wed, 15 Feb 2023 15:17:45 +0530 [thread overview]
Message-ID: <55f2d37f-9f60-a767-265f-86f75e77d5ab@nvidia.com> (raw)
In-Reply-To: <20221212222549.3779846-4-u.kleine-koenig@pengutronix.de>
On 13/12/22 03:55, Uwe Kleine-König wrote:
> External email: Use caution opening links or attachments
>
>
> A remove callback just returning 0 is equivalent to no remove callback
> at all. So drop the useless function.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Sumit Gupta <sumitg@nvidia.com>
> ---
> drivers/soc/tegra/cbb/tegra234-cbb.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/soc/tegra/cbb/tegra234-cbb.c b/drivers/soc/tegra/cbb/tegra234-cbb.c
> index 3528f9e15d5c..3b26dcf9a70c 100644
> --- a/drivers/soc/tegra/cbb/tegra234-cbb.c
> +++ b/drivers/soc/tegra/cbb/tegra234-cbb.c
> @@ -1066,11 +1066,6 @@ static int tegra234_cbb_probe(struct platform_device *pdev)
> return tegra_cbb_register(&cbb->base);
> }
>
> -static int tegra234_cbb_remove(struct platform_device *pdev)
> -{
> - return 0;
> -}
> -
> static int __maybe_unused tegra234_cbb_resume_noirq(struct device *dev)
> {
> struct tegra234_cbb *cbb = dev_get_drvdata(dev);
> @@ -1088,7 +1083,6 @@ static const struct dev_pm_ops tegra234_cbb_pm = {
>
> static struct platform_driver tegra234_cbb_driver = {
> .probe = tegra234_cbb_probe,
> - .remove = tegra234_cbb_remove,
> .driver = {
> .name = "tegra234-cbb",
> .of_match_table = tegra234_cbb_dt_ids,
> --
> 2.38.1
>
next prev parent reply other threads:[~2023-02-15 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 22:25 [PATCH 0/3] soc: " Uwe Kleine-König
2022-12-12 22:25 ` [PATCH 1/3] soc: bcm: bcm2835-power: " Uwe Kleine-König
2022-12-12 22:56 ` Florian Fainelli
2022-12-12 22:25 ` [PATCH 2/3] soc: mediatek: mutex: " Uwe Kleine-König
2022-12-13 9:50 ` AngeloGioacchino Del Regno
2022-12-16 12:27 ` Matthias Brugger
2022-12-12 22:25 ` [PATCH 3/3] soc: tegra: cbb: " Uwe Kleine-König
2023-01-12 21:55 ` Uwe Kleine-König
2023-02-15 7:47 ` Uwe Kleine-König
2023-02-15 9:47 ` Sumit Gupta [this message]
2023-04-05 12:41 ` (subset) " Thierry Reding
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=55f2d37f-9f60-a767-265f-86f75e77d5ab@nvidia.com \
--to=sumitg@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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®