From: Jiri Slaby <jirislaby@kernel.org>
To: Florian Eckert <fe@dev.tdt.de>
Cc: gregkh@linuxfoundation.org, kumaravel.thiagarajan@microchip.com,
tharunkumar.pasumarthi@microchip.com,
andriy.shevchenko@linux.intel.com, pnewman@connecttech.com,
angelogioacchino.delregno@collabora.com, peterz@infradead.org,
yujiaoliang@vivo.com, arnd@kernel.org, cang1@live.co.uk,
macro@orcam.me.uk, schnelle@linux.ibm.com,
Eckert.Florian@googlemail.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: 8250_pcilib: Replace deprecated PCI functions
Date: Mon, 29 Sep 2025 08:00:19 +0200 [thread overview]
Message-ID: <da2de297-2c9c-4855-9fb7-553022538cde@kernel.org> (raw)
In-Reply-To: <e4d2fa14701092977daa844cf25e7dd7@dev.tdt.de>
On 26. 09. 25, 14:31, Florian Eckert wrote:
>>> Signed-off-by: Florian Eckert <fe@dev.tdt.de>
>> ...
>>> --- a/drivers/tty/serial/8250/8250_pci.c
>>> +++ b/drivers/tty/serial/8250/8250_pci.c
>>> @@ -165,7 +165,15 @@ static int
>>> setup_port(struct serial_private *priv, struct uart_8250_port *port,
>>> u8 bar, unsigned int offset, int regshift)
>>> {
>>> - return serial8250_pci_setup_port(priv->dev, port, bar, offset,
>>> regshift);
>>> + void __iomem *iomem = NULL;
>>> +
>>> + if (pci_resource_flags(priv->dev, bar) & IORESOURCE_MEM) {
>>> + iomem = pcim_iomap(priv->dev, bar, 0);
>>> + if (IS_ERR(iomem))
>>> + return -ENOMEM;
>>
>> Why not to propagate the error?
>
> Most other calls in the kernel of this function return
> -ENOMEM on error. Therefore, I thought that this is the
> correct return value. I can fix that in v2 if you like.
> Let me know what you prefer.
Ugh, pcim_iomap() returns NULL on error, so the IS_ERR() check is all
wrong. What other places in the kernel use IS_ERR()? They need fixing.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-09-29 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 13:35 [PATCH] serial: 8250_pcilib: Replace deprecated PCI functions Florian Eckert
2025-09-26 8:29 ` Jiri Slaby
2025-09-26 12:31 ` Florian Eckert
2025-09-29 6:00 ` Jiri Slaby [this message]
2025-09-29 6:33 ` Florian Eckert
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=da2de297-2c9c-4855-9fb7-553022538cde@kernel.org \
--to=jirislaby@kernel.org \
--cc=Eckert.Florian@googlemail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@kernel.org \
--cc=cang1@live.co.uk \
--cc=fe@dev.tdt.de \
--cc=gregkh@linuxfoundation.org \
--cc=kumaravel.thiagarajan@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=peterz@infradead.org \
--cc=pnewman@connecttech.com \
--cc=schnelle@linux.ibm.com \
--cc=tharunkumar.pasumarthi@microchip.com \
--cc=yujiaoliang@vivo.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