devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] of: unittest: update text of expected warnings
Date: Tue, 1 Feb 2022 12:23:50 -0600	[thread overview]
Message-ID: <fb292c87-ea49-3837-40e7-a5d9031cdeb7@gmail.com> (raw)
In-Reply-To: <CAL_JsqLSsHJMKqOcLYR6uegghy8acLmu7iOX40gp__XVaShBUg@mail.gmail.com>

On 1/31/22 9:04 AM, Rob Herring wrote:
> 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.

I cleaned it up and submitted a patch.

-Frank

> 
> Rob
> 


      reply	other threads:[~2022-02-01 18:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 19:26 [PATCH 1/1] of: unittest: update text of expected warnings frowand.list
2022-01-31 14:35 ` Rob Herring
2022-01-31 15:04 ` Rob Herring
2022-02-01 18:23   ` Frank Rowand [this message]

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=fb292c87-ea49-3837-40e7-a5d9031cdeb7@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).