From: Markus Elfring <Markus.Elfring@web.de>
To: Reid Downing <skibletz@gmail.com>,
kernel-janitors@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] memory: fsl_ifc: Clear global controller pointer on probe failure and remove
Date: Fri, 30 Oct 2026 18:48:17 +0100 [thread overview]
Message-ID: <20729143-9d1e-4d8a-989c-c76f362c5612@web.de> (raw)
In-Reply-To: <20261025170833.1316443-1-skibletz@gmail.com>
…
> Clear the pointer on the probe error paths and in remove, once the IRQs
> have been released. The global cannot be published later in probe
…
???
Is there a need to refine the change description another bit?
…
> ---
> Changes in v3:
…
> Not compile-tested (no PowerPC build setup); the change is four
> assignments of NULL.
It seems that I am counting differently.
…
> +++ b/drivers/memory/fsl_ifc.c
…
> @@ -218,6 +220,7 @@ static int fsl_ifc_ctrl_probe(struct platform_device *dev)
> fsl_ifc_ctrl_dev->gregs = of_iomap(dev->dev.of_node, 0);
> if (!fsl_ifc_ctrl_dev->gregs) {
> dev_err(&dev->dev, "failed to get memory region\n");
> + fsl_ifc_ctrl_dev = NULL;
> return -ENODEV;
> }
>
> @@ -300,6 +303,7 @@ static int fsl_ifc_ctrl_probe(struct platform_device *dev)
> irq_dispose_mapping(fsl_ifc_ctrl_dev->irq);
> err:
> iounmap(fsl_ifc_ctrl_dev->gregs);
> + fsl_ifc_ctrl_dev = NULL;
> return ret;
> }
How do you think about to avoid duplicate source code a bit more?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?h=v7.3#n526
https://elixir.bootlin.com/linux/v7.3/source/drivers/memory/fsl_ifc.c#L194-L304
Regards,
Markus
prev parent reply other threads:[~2026-10-30 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 17:08 Reid Downing
2026-10-30 14:10 ` Krzysztof Kozlowski
2026-10-30 14:13 ` Krzysztof Kozlowski
2026-10-30 14:51 ` Reid Downing
2026-10-30 15:01 ` Krzysztof Kozlowski
2026-10-30 17:48 ` Markus Elfring [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=20729143-9d1e-4d8a-989c-c76f362c5612@web.de \
--to=markus.elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skibletz@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
all inboxes | Powered by JetHome®