Linux-MIPS Archive on lore.kernel.org
 help / color / Atom feed
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 2/3] MIPS: SGI-IP27: use generic PCI driver
Date: Tue, 7 May 2019 23:19:51 -0700
Message-ID: <20190508061951.GC19227@infradead.org> (raw)
In-Reply-To: <20190507210917.4691-3-tbogendoerfer@suse.de>

On Tue, May 07, 2019 at 11:09:14PM +0200, Thomas Bogendoerfer wrote:
> Converted bridge code to a platform driver using the PCI generic driver
> framework and use adding platform devices during xtalk scan. This allows
> easier sharing bridge driver for other SGI platforms like IP30 (Octane) and
> IP35 (Origin 3k, Fuel, Tezro).

Ok, here everything makes sense again.  Looks like it is just the
changelogs for the first two patches that might need minor updates.

The whole series looks conceptually fine to me, although I'm not sure
I'm qualified to review it.

  reply index

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 [this message]
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 ` [PATCH v4 00/3] MIPS: SGI-IP27 rework part2 Christoph Hellwig
2019-05-08  7:51   ` Thomas Bogendoerfer

Reply instructions:

You may reply publically 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=20190508061951.GC19227@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

Linux-MIPS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-mips/0 linux-mips/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-mips linux-mips/ https://lore.kernel.org/linux-mips \
		linux-mips@vger.kernel.org linux-mips@archiver.kernel.org
	public-inbox-index linux-mips


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-mips


AGPL code for this site: git clone https://public-inbox.org/ public-inbox