[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYPoZX1+rfJb925_+H6YXiwO26cKLpZae=_j=RQKGA0Wg@mail.gmail.com>
Date: Wed, 30 Sep 2020 10:47:17 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Sean Wang <sean.wang@...nel.org>
Cc: Enric Balletbo i Serra <enric.balletbo@...labora.com>,
lkml <linux-kernel@...r.kernel.org>,
Collabora Kernel ML <kernel@...labora.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Nicolas Boichat <drinkcat@...omium.org>, hsinyi@...omium.org,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>
Subject: Re: [PATCH v2] pinctrl: mediatek: Free eint data on failure
On Sun, Sep 27, 2020 at 7:57 PM Sean Wang <sean.wang@...nel.org> wrote:
> v2 seems the same with v1 or I was missing something.
>
> I just thought we call devm_ioremap_release to explicitly to free
> resource when a certain failure occurs after
> devm_ioremap_resource?
What is the semantics around mtk_build_eint()?
If it is called on the probe path no explicit free:ing is
necessary: anytime probe() exits with an error code,
any devm* resources will be free:ed.
Yours,
Linus Walleij
Powered by blists - more mailing lists