From: Damien Le Moal <dlemoal@kernel.org>
To: Chen Ni <nichen@iscas.ac.cn>, s.shtylyov@omp.ru, jeff@garzik.org
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata_isapnp: Add check for devm_ioport_map
Date: Tue, 31 Oct 2023 14:20:30 +0900 [thread overview]
Message-ID: <3a5495de-8ef9-4362-aa26-86a31c6aa315@kernel.org> (raw)
In-Reply-To: <4916b09e-ec4b-4106-bd1a-1b86827d8901@kernel.org>
On 10/31/23 14:13, Damien Le Moal wrote:
> On 10/31/23 13:00, Chen Ni wrote:
>> Add check for devm_ioport_map() and return the error if it fails in
>> order to guarantee the success of devm_ioport_map().
>>
>> Fixes: 0d5ff566779f ("libata: convert to iomap")
>
> This is the wrong patch. That patch was using pcim_iomap_regions(), not
> devm_ioport_map().
Please ignore. I did not read that patch properly. This is fine.
The fixes tag is not really needed anyway.
>
>> Signed-off-by: Chen Ni <nichen@iscas.ac.cn>
>> ---
>> drivers/ata/pata_isapnp.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/ata/pata_isapnp.c b/drivers/ata/pata_isapnp.c
>> index 25a63d043c8e..0f77e0424066 100644
>> --- a/drivers/ata/pata_isapnp.c
>> +++ b/drivers/ata/pata_isapnp.c
>> @@ -82,6 +82,9 @@ static int isapnp_init_one(struct pnp_dev *idev, const struct pnp_device_id *dev
>> if (pnp_port_valid(idev, 1)) {
>> ctl_addr = devm_ioport_map(&idev->dev,
>> pnp_port_start(idev, 1), 1);
>> + if (!ctl_addr)
>> + return -ENOMEM;
>> +
>> ap->ioaddr.altstatus_addr = ctl_addr;
>> ap->ioaddr.ctl_addr = ctl_addr;
>> ap->ops = &isapnp_port_ops;
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-10-31 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 4:00 [PATCH] pata_isapnp: Add check for devm_ioport_map Chen Ni
2023-10-31 5:13 ` Damien Le Moal
2023-10-31 5:20 ` Damien Le Moal [this message]
2023-10-31 15:18 ` Sergey Shtylyov
2023-11-10 1:01 ` Damien Le Moal
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=3a5495de-8ef9-4362-aa26-86a31c6aa315@kernel.org \
--to=dlemoal@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=nichen@iscas.ac.cn \
--cc=s.shtylyov@omp.ru \
/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