From: Christoph Hellwig <hch@infradead.org>
To: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/3] MIPS: SGI-IP27 rework part2
Date: Tue, 7 May 2019 23:16:29 -0700 [thread overview]
Message-ID: <20190508061629.GA19227@infradead.org> (raw)
In-Reply-To: <20190507210917.4691-1-tbogendoerfer@suse.de>
On Tue, May 07, 2019 at 11:09:12PM +0200, Thomas Bogendoerfer wrote:
> SGI IP27 (Origin/Onyx2) and SGI IP30 (Octane) have a similair
Typo s/similair/similar/
> architecture and share some hardware (ioc3/bridge). To share
Isn't much of this also shared by IP35, the next generation Origin/Onyx
and and co? A quick web search shows there even is an early port to
IP35 here:
http://git.linux-mips.org/cgit/nyef/linux-ip35/log/?h=sgi-ip35-v4.2-2015-10-24
next prev parent reply other threads:[~2019-05-08 6:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 21:09 [PATCH v4 00/3] MIPS: SGI-IP27 rework part2 Thomas Bogendoerfer
2019-05-07 21:09 ` [PATCH v4 1/3] MIPS: SGI-IP27: move IP27 specific code out of pci-ip27.c into new file Thomas Bogendoerfer
2019-05-08 6:18 ` Christoph Hellwig
2019-05-08 7:52 ` Thomas Bogendoerfer
2019-05-09 23:54 ` Paul Burton
2019-05-10 14:16 ` Thomas Bogendoerfer
2019-05-07 21:09 ` [PATCH v4 2/3] MIPS: SGI-IP27: use generic PCI driver Thomas Bogendoerfer
2019-05-08 6:19 ` Christoph Hellwig
2019-05-09 23:52 ` Paul Burton
2019-05-07 21:09 ` [PATCH v4 3/3] MIPS: SGI-IP27: abstract chipset irq from bridge Thomas Bogendoerfer
2019-05-09 23:52 ` Paul Burton
2019-05-08 6:16 ` Christoph Hellwig [this message]
2019-05-08 7:51 ` [PATCH v4 00/3] MIPS: SGI-IP27 rework part2 Thomas Bogendoerfer
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=20190508061629.GA19227@infradead.org \
--to=hch@infradead.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--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).