[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJ1=5ABi5N50HLTSu2xFGJJSf-6EpuvhkG-rxSbv3MZdw@mail.gmail.com>
Date: Wed, 24 Oct 2018 14:57:31 -0500
From: Rob Herring <robh+dt@...nel.org>
To: Alan Tull <atull@...nel.org>
Cc: Frank Rowand <frowand.list@...il.com>,
Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Michael Ellerman <mpe@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Moritz Fischer <mdf@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
devicetree@...r.kernel.org, linux-fpga@...r.kernel.org
Subject: Re: [PATCH v5 00/18] of: overlay: validation checks, subsequent fixes
On Mon, Oct 22, 2018 at 4:25 PM Alan Tull <atull@...nel.org> wrote:
>
> On Thu, Oct 18, 2018 at 5:48 PM <frowand.list@...il.com> wrote:
> >
> > From: Frank Rowand <frank.rowand@...y.com>
> >
> > Add checks to (1) overlay apply process and (2) memory freeing
> > triggered by overlay release. The checks are intended to detect
> > possible memory leaks and invalid overlays.
>
> I've tested v5, nothing new to report.
Does that mean everything broken or everything works great? In the
latter case, care to give a Tested-by.
Rob
Powered by blists - more mailing lists