linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Maik Nassauer <maik.nassauer@kernelconcepts.de>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: Non deterministic kernel crashes after minimal devicetree changes.
Date: Mon, 22 Jul 2019 11:14:56 +0200	[thread overview]
Message-ID: <bd4b0e25d5c1c5356b2139442360df27a3ea975f.camel@kernelconcepts.de> (raw)
In-Reply-To: <513a3742d2a3a932b4958dc1b5fd68342aa43e41.camel@kernelconcepts.de>

[-- Attachment #1: Type: text/plain, Size: 357 bytes --]

Any ideas how to deal with this problem? 

Best regards

-- 
kernel concepts GmbH               Maik Nassauer
Hauptstraße 16                               
maik.nassauer@kernelconcepts.de
D-57074 Siegen                             Tel: +49 271-338857-21
http://www.kernelconcepts.de/      
HR Siegen, HR B 9613
Geschäftsführer: Ole Reinhardt

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 878 bytes --]

      reply	other threads:[~2019-07-22  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 15:50 Non deterministic kernel crashes after minimal devicetree changes Maik Nassauer
2019-07-22  9:14 ` Maik Nassauer [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=bd4b0e25d5c1c5356b2139442360df27a3ea975f.camel@kernelconcepts.de \
    --to=maik.nassauer@kernelconcepts.de \
    --cc=linuxppc-dev@lists.ozlabs.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).