From: Carlo Pisani <carlojpisani@gmail.com>
To: Matt Turner <mattst88@gmail.com>
Cc: "Joshua Kinard" <kumba@gentoo.org>,
"Paul Burton" <paul.burton@mips.com>,
"Thomas Bogendoerfer" <tbogendoerfer@suse.de>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"René Rebe" <rene@exactcode.com>
Subject: Re: SGI-IP30
Date: Fri, 28 Jun 2019 10:27:10 +0200 [thread overview]
Message-ID: <CA+QBN9B33Crhyahn5SXZJY8Pk7tDnhqgReuJKx5FhgguG=GXWg@mail.gmail.com> (raw)
In-Reply-To: <CA+QBN9DO9sAadwFU6kpAfBxZuTVEx8_9DUYFBs6fTA6==cVDwQ@mail.gmail.com>
guys
I have just tested the shoehorn in SlotC: there are quirks, but at
least the kernel doesn't panic
to summarize:
ShoeHorn in XIO-SlotA: panics
ShoeHorn in XIO-SlotB: not yet tested
ShoeHorn in XIO-SlotC: doesn't panic
ShoeHorn in XIO-SlotD: panics
- UP -
A | B
D | C
ShoeBox: doesn't panic
next prev parent reply other threads:[~2019-06-28 8:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 12:40 Call trace stops at static callback functions Hauke Mehrtens
2019-06-22 12:42 ` SGI-IP30 Carlo Pisani
2019-06-24 17:55 ` SGI-IP30 Paul Burton
2019-06-24 19:16 ` SGI-IP30 Maciej W. Rozycki
2019-06-25 8:59 ` SGI-IP30 Thomas Bogendoerfer
2019-06-26 4:23 ` SGI-IP30 Joshua Kinard
2019-06-26 5:49 ` SGI-IP30 Carlo Pisani
2019-07-01 19:27 ` SGI-IP30 Joshua Kinard
2019-06-27 20:38 ` SGI-IP30 Matt Turner
2019-06-27 22:29 ` SGI-IP30 Carlo Pisani
2019-06-28 8:27 ` Carlo Pisani [this message]
2019-07-01 18:31 ` SGI-IP30 Joshua Kinard
2019-07-01 18:36 ` SGI-IP30 Carlo Pisani
2019-07-01 20:29 ` SGI-IP30 Joshua Kinard
2019-07-01 20:41 ` SGI-IP30 Carlo Pisani
2019-06-28 9:46 ` SGI-IP30 Carlo Pisani
2019-06-24 18:10 ` Call trace stops at static callback functions Paul Burton
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='CA+QBN9B33Crhyahn5SXZJY8Pk7tDnhqgReuJKx5FhgguG=GXWg@mail.gmail.com' \
--to=carlojpisani@gmail.com \
--cc=kumba@gentoo.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=paul.burton@mips.com \
--cc=rene@exactcode.com \
--cc=tbogendoerfer@suse.de \
/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).