linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Rob Herring <robh@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.12-rc5
Date: Mon, 29 Mar 2021 12:42:58 -0700	[thread overview]
Message-ID: <1f047022-f74f-e738-d683-d6ae45d3ce49@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wiMoP9PifpuUnQ3xmAM_LmGARr+fxFuOSX1rvh2mz35Mw@mail.gmail.com>

On 3/29/21 11:05 AM, Linus Torvalds wrote:
> On Sun, Mar 28, 2021 at 7:07 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> This is not really a new problem. I enabled devicetree unit tests
>> in the openrisc kernel and was rewarded with a crash.
>> https://lore.kernel.org/lkml/20210327224116.69309-1-linux@roeck-us.net/
>> has all the glorious details.
> 
> Hmm.
> 
> I'm not sure I love that patch.
> 

Me not either. I did point out that it doesn't fix the problem, only
the impact. Fixing the dt unittest code would have been easy enough,
but I wasn't sure how to properly address the problem in the dt overlay
code, and I was concerned that other code might be affected as well,
so I gave up trying and settled on error handling.

Looks like Frank is going to provide a proper fix, so we should be covered.

Thanks,
Guenter

      parent reply	other threads:[~2021-03-29 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28 23:05 Linux 5.12-rc5 Linus Torvalds
2021-03-29  2:07 ` Guenter Roeck
2021-03-29 18:05   ` Linus Torvalds
2021-03-29 18:41     ` Rob Herring
2021-03-29 19:04       ` Frank Rowand
2021-03-29 19:42     ` Guenter Roeck [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=1f047022-f74f-e738-d683-d6ae45d3ce49@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=torvalds@linux-foundation.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).