From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Aaron Kling <webgeek1234@gmail.com>
Subject: Re: [PATCH v2 08/13] memory: tegra186-emc: Simplify and handle deferred probe with dev_err_probe()
Date: Thu, 6 Nov 2025 13:13:04 +0100 [thread overview]
Message-ID: <1db683cc-ffce-48da-ad2f-e25ed901ce00@kernel.org> (raw)
In-Reply-To: <4ba8a1ec-fa17-4564-a174-0b8e8eada061@nvidia.com>
On 06/11/2025 13:04, Jon Hunter wrote:
>> @@ -319,14 +318,13 @@ static int tegra186_emc_probe(struct platform_device *pdev)
>>
>> emc->bpmp = tegra_bpmp_get(&pdev->dev);
>> if (IS_ERR(emc->bpmp))
>> - return dev_err_probe(&pdev->dev, PTR_ERR(emc->bpmp), "failed to get BPMP\n");
>> + return dev_err_probe(&pdev->dev, PTR_ERR(emc->bpmp),
>> + "failed to get BPMP\n");
>>
>> emc->clk = devm_clk_get(&pdev->dev, "emc");
>> - if (IS_ERR(emc->clk)) {
>> - err = PTR_ERR(emc->clk);
>> - dev_err(&pdev->dev, "failed to get EMC clock: %d\n", err);
>> - goto put_bpmp;
>> - }
>> + if (IS_ERR(emc->clk))
>> + return dev_err_probe(&pdev->dev, PTR_ERR(emc->clk),
>> + "failed to get EMC clock\n");
>
> I see now that we dropped a 'put_bpmp' here and we should not have. I
> see this is in -next, do you want fix up or I can send a patch?
Indeed, thanks for noticing this. Please send a patch with Fixes tag.
Will you also take a look at other patches from this patchset, if I did
not make same mistake?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-06 12:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 9:43 [PATCH v2 00/13] memory: tegra: Several cleanups Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 01/13] memory: tegra124-emc: Simplify return of emc_init() Krzysztof Kozlowski
2025-09-17 13:12 ` Jon Hunter
2025-09-11 9:43 ` [PATCH v2 02/13] memory: tegra124-emc: Do not print error on icc_node_create() failure Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 03/13] memory: tegra186-emc: " Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 04/13] memory: tegra20-emc: " Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 05/13] memory: tegra30-emc: " Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 06/13] memory: tegra30-emc: Simplify and handle deferred probe with dev_err_probe() Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 07/13] memory: tegra20-emc: " Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 08/13] memory: tegra186-emc: " Krzysztof Kozlowski
2025-11-06 12:04 ` Jon Hunter
2025-11-06 12:13 ` Krzysztof Kozlowski [this message]
2025-11-06 14:14 ` Jon Hunter
2025-11-06 14:43 ` Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 09/13] memory: tegra124-emc: " Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 10/13] memory: tegra124-emc: Add the SoC model prefix to functions Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 11/13] memory: tegra186-emc: " Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 12/13] memory: tegra20-emc: " Krzysztof Kozlowski
2025-09-11 9:43 ` [PATCH v2 13/13] memory: tegra30-emc: " Krzysztof Kozlowski
2025-09-17 13:13 ` [PATCH v2 00/13] memory: tegra: Several cleanups Jon Hunter
2025-10-13 0:23 ` Krzysztof Kozlowski
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=1db683cc-ffce-48da-ad2f-e25ed901ce00@kernel.org \
--to=krzk@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=webgeek1234@gmail.com \
/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