From: Aisheng Dong <aisheng.dong@nxp.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
dl-linux-imx <linux-imx@nxp.com>
Cc: "shawnguo@kernel.org" <shawnguo@kernel.org>
Subject: RE: [PATCH -next v2 1/2] ARM: imx: add missing iounmap()
Date: Thu, 17 Jun 2021 12:20:02 +0000 [thread overview]
Message-ID: <DB9PR04MB84778C8658880848D18AE2F4800E9@DB9PR04MB8477.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210615125239.1348845-2-yangyingliang@huawei.com>
> From: Yang Yingliang <yangyingliang@huawei.com>
> Sent: Tuesday, June 15, 2021 8:53 PM
> Subject: [PATCH -next v2 1/2] ARM: imx: add missing iounmap()
>
> Commit e76bdfd7403a ("ARM: imx: Added perf functionality to mmdc driver")
> introduced imx_mmdc_remove(), the mmdc_base need be unmapped in it if
> config PERF_EVENTS is enabled.
>
> If imx_mmdc_perf_init() fails, the mmdc_base also need be unmapped.
>
> Fixes: e76bdfd7403a ("ARM: imx: Added perf functionality to mmdc driver")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
Regards
Aisheng
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-17 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 12:52 [PATCH -next v2 0/2] ARM: imx: free resources Yang Yingliang
2021-06-15 12:52 ` [PATCH -next v2 1/2] ARM: imx: add missing iounmap() Yang Yingliang
2021-06-17 12:20 ` Aisheng Dong [this message]
2021-06-15 12:52 ` [PATCH -next v2 2/2] ARM: imx: add missing clk_disable_unprepare() Yang Yingliang
2021-06-17 12:20 ` Aisheng Dong
2021-07-14 7:19 ` [PATCH -next v2 0/2] ARM: imx: free resources Shawn Guo
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=DB9PR04MB84778C8658880848D18AE2F4800E9@DB9PR04MB8477.eurprd04.prod.outlook.com \
--to=aisheng.dong@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=yangyingliang@huawei.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;
as well as URLs for NNTP newsgroup(s).