linux-kernel - Re: [PATCH] mediatek/clk-mt8173-apmixedsys: use devm_of_iomap to avoid resource leak in clk_mt8173_apmixed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <7F568F0F-1F19-4302-8BBB-556146B3C521@163.com>
Date:   Thu, 11 May 2023 09:56:35 +0800
From:   Hao Ge <gehao618@....com>
To:     Stephen Boyd <sboyd@...nel.org>
Cc:     Hao Ge <gehao@...inos.cn>, angelogioacchino.delregno@...labora.com,
        matthias.bgg@...il.com, mturquette@...libre.com,
        wenst@...omium.org, linux-clk@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] mediatek/clk-mt8173-apmixedsys: use devm_of_iomap to avoid resource leak in clk_mt8173_apmixed_probe



> On May 11, 2023, at 09:27, Hao Ge <gehao618@....com> wrote:
> 
> On Wed, 10 May 2023 14:18:08 -0700
> Stephen Boyd <sboyd@...nel.org> wrote:
> 
>> Quoting Hao Ge (2023-05-08 19:12:14)
>>> Use devm_platform_ioremap_resource to take the place of of_iomap for
>>> avoid that we don't called iounmap when return some error or remove
>>> device.
>>> Fixes: 4c02c9af3cb9 ("clk: mediatek: mt8173: Break down clock
>>> drivers and allow module build") Signed-off-by: Hao Ge
>>> <gehao@...inos.cn> ---  
>> Is this v3?
> Hi Stephen
> 
> yes,Perhaps you are too busy,I have not received a response
> in the future, so you are unsure about the status of V2.
> So I adjusted the code and title make changes smaller and
> sent V3 for it.It is precisely because of these that I did 
> not continue the original mail thread.
> 
> Best regards
> Hao
Hi Stephen

I made a few typos in my previous email. To avoid misunderstandings, I corrected them and sent a new one.

Yes,Perhaps you are too busy,I have not received a response in the future, so I am unsure about the status of V2.So I adjusted the code and title make changes smaller and
sent V3 for it.It is precisely because of these that I did not continue the original mail thread.

Best regards
Hao