From: Dongliang Mu <mudongliangabcd@gmail.com>
To: Samuel Iglesias Gonsalvez <siglesias@igalia.com>,
Jens Taprogge <jens.taprogge@taprogge.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dongliang Mu <mudongliangabcd@gmail.com>,
Aditya Srivastava <yashsri421@gmail.com>,
Lv Yunlong <lyl2019@mail.ustc.edu.cn>
Cc: Randy Dunlap <rdunlap@infradead.org>,
industrypack-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] ipack: tpci200: pci_iounmap -> iounmap
Date: Wed, 21 Jul 2021 19:11:30 +0800 [thread overview]
Message-ID: <20210721111137.1523229-1-mudongliangabcd@gmail.com> (raw)
The deallocation api for ioremap should be iounmap, other than
pci_iounmap.
Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
---
drivers/ipack/carriers/tpci200.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/ipack/carriers/tpci200.c b/drivers/ipack/carriers/tpci200.c
index 3461b0a7dc62..ca302a87bc22 100644
--- a/drivers/ipack/carriers/tpci200.c
+++ b/drivers/ipack/carriers/tpci200.c
@@ -88,8 +88,8 @@ static void tpci200_unregister(struct tpci200_board *tpci200)
{
free_irq(tpci200->info->pdev->irq, (void *) tpci200);
- pci_iounmap(tpci200->info->pdev, tpci200->info->interface_regs);
- pci_iounmap(tpci200->info->pdev, tpci200->info->cfg_regs);
+ iounmap(tpci200->info->interface_regs);
+ iounmap(tpci200->info->cfg_regs);
pci_release_region(tpci200->info->pdev, TPCI200_IP_INTERFACE_BAR);
pci_release_region(tpci200->info->pdev, TPCI200_IO_ID_INT_SPACES_BAR);
--
2.25.1
next reply other threads:[~2021-07-21 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 11:11 Dongliang Mu [this message]
2021-07-21 11:11 ` [PATCH 2/3] ipack: tpci200: fix many double free issues in tpci200_pci_probe Dongliang Mu
2021-08-05 12:20 ` Greg Kroah-Hartman
2021-08-09 3:40 ` Dongliang Mu
2021-08-09 8:45 ` Greg Kroah-Hartman
2021-07-21 11:11 ` [PATCH 3/3] ipack: tpci200: fix memory leak in the tpci200_register Dongliang Mu
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=20210721111137.1523229-1-mudongliangabcd@gmail.com \
--to=mudongliangabcd@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=industrypack-devel@lists.sourceforge.net \
--cc=jens.taprogge@taprogge.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyl2019@mail.ustc.edu.cn \
--cc=rdunlap@infradead.org \
--cc=siglesias@igalia.com \
--cc=yashsri421@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
Powered by JetHome