Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 16 Apr 2020 17:10:06 -0500
From:   Rob Herring <robh@kernel.org>
To:     frowand.list@gmail.com
Cc:     pantelis.antoniou@konsulko.com, devicetree@vger.kernel.org,
        linux-kernel@vger.kernel.org,
        Michael Ellerman <mpe@ellerman.id.au>,
        "Erhard F." <erhard_f@mailbox.org>,
        Geert Uytterhoeven <geert+renesas@glider.be>,
        Alan Tull <atull@kernel.org>
Subject: Re: [PATCH 0/5] of: unittest: kmleak detected memory leaks
Message-ID: <20200416221006.GA3834@bogus>
References: <1587073370-25963-1-git-send-email-frowand.list@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1587073370-25963-1-git-send-email-frowand.list@gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Apr 16, 2020 at 04:42:45PM -0500, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
> 
> Original bug report:
>   https://bugzilla.kernel.org/show_bug.cgi?id=206203
>   https://lore.kernel.org/r/877dyqlles.fsf@mpe.ellerman.id.au
> 
> kmemleak detected many memory leaks originating if devicetree
> unittests.
> 
> Five separate causes were found.  Four causes were bugs and
> one was expected.
> 
> Fix the four bugs and modify the test that led to the expected
> memory leak to no longer have a memory leak.
> 
> 
> Frank Rowand (5):
>   of: unittest: kmemleak on changeset destroy
>   of: unittest: kmemleak in of_unittest_platform_populate()
>   of: unittest: kmemleak in of_unittest_overlay_high_level()
>   of: overlay: kmemleak in dup_and_fixup_symbol_prop()
>   of: unittest: kmemleak in duplicate property update

Series applied. (To get into today's -next and I plan to send to Linus 
tomorrow.)

Rob