From: Frank Rowand <frowand.list@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Colin King <colin.king@canonical.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] of: overlay: Fix of_overlay_apply() error path
Date: Tue, 5 Dec 2017 21:40:33 -0500 [thread overview]
Message-ID: <48dd6ac2-6481-4164-6051-ec9fd98490fb@gmail.com> (raw)
In-Reply-To: <1512487623-30450-1-git-send-email-geert+renesas@glider.be>
On 12/05/17 10:27, Geert Uytterhoeven wrote:
> Hi Pantelis, Rob, Frank,
>
> Here's a replacement for commit bd80e2555c5c9d45 ("of: overlay: Fix
> cleanup order in of_overlay_apply()"), which was applied by Rob, and
> dropped later.
>
> The first patch fixes the memory leak reported by Colin.
> The second patch is a replacement for the bad dropped commit, and
> depends on the first patch for proper cleanup.
>
> All OF unittests pass.
>
> Thanks!
>
> Geert Uytterhoeven (2):
> of: overlay: Fix memory leak in of_overlay_apply() error path
> of: overlay: Fix (un)locking in of_overlay_apply()
>
> drivers/of/overlay.c | 31 +++++++++++++------------------
> 1 file changed, 13 insertions(+), 18 deletions(-)
>
Thank you, the code is much improved by these patches.
Reviewed-by: Frank Rowand <frank.rowand@sony.com>
next prev parent reply other threads:[~2017-12-06 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 15:27 Geert Uytterhoeven
2017-12-05 15:27 ` [PATCH v3 1/2] of: overlay: Fix memory leak in " Geert Uytterhoeven
2017-12-05 15:27 ` [PATCH v3 2/2] of: overlay: Fix (un)locking in of_overlay_apply() Geert Uytterhoeven
2017-12-06 2:40 ` Frank Rowand [this message]
2017-12-06 22:07 ` [PATCH v3 0/2] of: overlay: Fix of_overlay_apply() error path Rob Herring
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=48dd6ac2-6481-4164-6051-ec9fd98490fb@gmail.com \
--to=frowand.list@gmail.com \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®