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;
MIME-Version: 1.0
References: <20220127192643.2534941-1-frowand.list@gmail.com>
In-Reply-To: <20220127192643.2534941-1-frowand.list@gmail.com>
From:   Rob Herring <robh+dt@kernel.org>
Date:   Mon, 31 Jan 2022 09:04:17 -0600
Message-ID: <CAL_JsqLSsHJMKqOcLYR6uegghy8acLmu7iOX40gp__XVaShBUg@mail.gmail.com>
Subject: Re: [PATCH 1/1] of: unittest: update text of expected warnings
To:     Frank Rowand <frowand.list@gmail.com>
Cc:     devicetree@vger.kernel.org,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Jan 27, 2022 at 1:26 PM <frowand.list@gmail.com> wrote:
>
> From: Frank Rowand <frank.rowand@sony.com>
>
> The text of various warning messages triggered by unittest has
> changed.  Update the text of expected warnings to match.
>
> The expected vs actual warnings are most easily seen by filtering
> the boot console messages with the of_unittest_expect program at
> https://github.com/frowand/dt_tools.git.  The filter prefixes

News to me there's such a tool. Normally, I just give up staring at
the wall of text spewed out and check failures. Can we add this tool
to the kernel tree? Then there might be some hope that I'll run it.

Rob