From: Kevin Hilman <khilman@baylibre.com>
To: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>, Bin Liu <b-liu@ti.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 5/5] usb: musb: omap2430: clean up probe error handling
Date: Wed, 30 Jul 2025 15:33:47 -0700 [thread overview]
Message-ID: <7ho6t1b96c.fsf@baylibre.com> (raw)
In-Reply-To: <20250724091910.21092-6-johan@kernel.org>
Johan Hovold <johan@kernel.org> writes:
> Using numbered error labels is discouraged (e.g. as it requires
> renumbering them when adding a new intermediate error path).
>
> Rename the error labels after what they do.
>
> While at it, drop the redundant platform allocation failure dev_err()
> as the error would already have been logged by the allocator.
>
> Signed-off-by: Johan Hovold <johan@kernel.org>
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
> ---
> drivers/usb/musb/omap2430.c | 23 ++++++++++-------------
> 1 file changed, 10 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c
> index 36f756f9b7f6..c35c07b7488c 100644
> --- a/drivers/usb/musb/omap2430.c
> +++ b/drivers/usb/musb/omap2430.c
> @@ -318,13 +318,11 @@ static int omap2430_probe(struct platform_device *pdev)
>
> glue = devm_kzalloc(&pdev->dev, sizeof(*glue), GFP_KERNEL);
> if (!glue)
> - goto err0;
> + return -ENOMEM;
>
> musb = platform_device_alloc("musb-hdrc", PLATFORM_DEVID_AUTO);
> - if (!musb) {
> - dev_err(&pdev->dev, "failed to allocate musb device\n");
> - goto err0;
> - }
> + if (!musb)
> + return -ENOMEM;
>
> musb->dev.parent = &pdev->dev;
> musb->dev.dma_mask = &omap2430_dmamask;
> @@ -349,15 +347,15 @@ static int omap2430_probe(struct platform_device *pdev)
>
> pdata = devm_kzalloc(&pdev->dev, sizeof(*pdata), GFP_KERNEL);
> if (!pdata)
> - goto err2;
> + goto err_put_musb;
>
> data = devm_kzalloc(&pdev->dev, sizeof(*data), GFP_KERNEL);
> if (!data)
> - goto err2;
> + goto err_put_musb;
>
> config = devm_kzalloc(&pdev->dev, sizeof(*config), GFP_KERNEL);
> if (!config)
> - goto err2;
> + goto err_put_musb;
>
> of_property_read_u32(np, "mode", (u32 *)&pdata->mode);
> of_property_read_u32(np, "interface-type",
> @@ -380,7 +378,7 @@ static int omap2430_probe(struct platform_device *pdev)
> if (!control_pdev) {
> dev_err(&pdev->dev, "Failed to get control device\n");
> ret = -EINVAL;
> - goto err2;
> + goto err_put_musb;
> }
> glue->control_otghs = &control_pdev->dev;
> }
> @@ -456,20 +454,19 @@ static int omap2430_probe(struct platform_device *pdev)
> ret = platform_device_add(musb);
> if (ret) {
> dev_err(&pdev->dev, "failed to register musb device\n");
> - goto err3;
> + goto err_disable_rpm;
> }
>
> return 0;
>
> -err3:
> +err_disable_rpm:
> pm_runtime_disable(glue->dev);
> err_put_control_otghs:
> if (!IS_ERR(glue->control_otghs))
> put_device(glue->control_otghs);
> -err2:
> +err_put_musb:
> platform_device_put(musb);
>
> -err0:
> return ret;
> }
>
> --
> 2.49.1
prev parent reply other threads:[~2025-07-30 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 9:19 [PATCH 0/5] USB: fix device leaks at unbind Johan Hovold
2025-07-24 9:19 ` [PATCH 1/5] usb: dwc3: imx8mp: fix device leak " Johan Hovold
2025-07-24 9:19 ` [PATCH 2/5] usb: dwc3: meson-g12a: fix device leaks " Johan Hovold
2025-07-24 20:40 ` Martin Blumenstingl
2025-07-24 9:19 ` [PATCH 3/5] usb: gadget: udc: renesas_usb3: fix device leak " Johan Hovold
2025-07-24 9:19 ` [PATCH 4/5] usb: musb: omap2430: " Johan Hovold
2025-07-30 22:33 ` Kevin Hilman
2025-07-24 9:19 ` [PATCH 5/5] usb: musb: omap2430: clean up probe error handling Johan Hovold
2025-07-30 22:33 ` Kevin Hilman [this message]
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=7ho6t1b96c.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=b-liu@ti.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=johan@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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
all inboxes | Powered by JetHome®