From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Charles Han <hanchunchao@inspur.com>, <broonie@kernel.org>,
<mcoquelin.stm32@gmail.com>, <alexandre.torgue@foss.st.com>
Cc: <linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: stm32: Fix a NULL vs IS_ERR() bug
Date: Fri, 7 Mar 2025 09:59:42 +0100 [thread overview]
Message-ID: <dfd831ec-e004-4132-94f0-3bdc755907cd@foss.st.com> (raw)
In-Reply-To: <20250307032530.116837-1-hanchunchao@inspur.com>
On 3/7/25 04:25, Charles Han wrote:
> The devm_ioremap() function doesn't return error pointers, it may
> returns NULL. Update the error checking to match.
>
> Fixes: 79b8a705e26c ("spi: stm32: Add OSPI driver")
> Signed-off-by: Charles Han <hanchunchao@inspur.com>
> ---
> drivers/spi/spi-stm32-ospi.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/spi/spi-stm32-ospi.c b/drivers/spi/spi-stm32-ospi.c
> index 8eadcb64f34a..a544d7897edf 100644
> --- a/drivers/spi/spi-stm32-ospi.c
> +++ b/drivers/spi/spi-stm32-ospi.c
> @@ -835,10 +835,10 @@ static int stm32_ospi_get_resources(struct platform_device *pdev)
> if (rmem) {
> ospi->mm_size = rmem->size;
> ospi->mm_base = devm_ioremap(dev, rmem->base, rmem->size);
> - if (IS_ERR(ospi->mm_base)) {
> + if (!ospi->mm_base) {
> dev_err(dev, "unable to map memory region: %pa+%pa\n",
> &rmem->base, &rmem->size);
> - ret = PTR_ERR(ospi->mm_base);
> + ret = -ENOMEM;
> goto err_dma;
> }
>
Hi
No need to copy/paste other contributor's patch by just swapping some
words in title/commit message.
This fix has already sent By Dan Carpenter and merged.
Patrice
next prev parent reply other threads:[~2025-03-07 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 3:25 Charles Han
2025-03-07 8:59 ` Patrice CHOTARD [this message]
2025-03-07 13:24 ` Mark Brown
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=dfd831ec-e004-4132-94f0-3bdc755907cd@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=hanchunchao@inspur.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@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®