From: David Miller <davem@davemloft.net>
To: benh@kernel.crashing.org
Cc: linux-pci@vger.kernel.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, bheglaas@google.com,
monstr@monstr.eu, tglx@linuxtronix.de, bigeasy@linuxtronix.de
Subject: Re: [PATCHES] Generalize PCI <-> OF node matching
Date: Thu, 07 Apr 2011 15:16:36 -0700 (PDT) [thread overview]
Message-ID: <20110407.151636.183068185.davem@davemloft.net> (raw)
In-Reply-To: <1302146796-26825-1-git-send-email-benh@kernel.crashing.org>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Thu, 7 Apr 2011 13:26:31 +1000
> This series generalize the PCI <-> OF node matching, moves it to the
> PCI core and make our archs use it. I also rip out while at it a whole
> bunch of useless stuff from microblaze PCI code which was copied from
> ppc32 and is essentially useless there (old workarounds for PowerMac
> and ancient X servers).
>
> Compile tested on x86_64, microblaze, sparc64 and powerpc.
What tree is this against? None of the microblaze and x86 bits
apply without rejects against Linus's tree, which is where I'm
trying to test this.
I'll trudge through it, but a heads up about what your patches
are against in the future would be heavily appreciated.
next prev parent reply other threads:[~2011-04-07 22:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 3:26 [PATCHES] Generalize PCI <-> OF node matching Benjamin Herrenschmidt
2011-04-07 3:26 ` Benjamin Herrenschmidt
2011-04-07 3:26 ` [PATCH 1/5] pci/of: Match PCI devices to OF nodes dynamically Benjamin Herrenschmidt
2011-04-07 4:20 ` Benjamin Herrenschmidt
2011-04-07 7:56 ` Sebastian Andrzej Siewior
2011-04-07 7:56 ` Sebastian Andrzej Siewior
2011-04-07 12:13 ` [PATCH] x86/ce4100: add reg property to bridges Sebastian Andrzej Siewior
2011-04-07 21:52 ` Benjamin Herrenschmidt
2011-04-11 7:23 ` Sebastian Andrzej Siewior
2011-04-11 9:38 ` Benjamin Herrenschmidt
2011-04-11 9:38 ` Benjamin Herrenschmidt
2011-04-07 22:27 ` [PATCH 1/5] pci/of: Match PCI devices to OF nodes dynamically David Miller
2011-04-07 22:27 ` David Miller
2011-04-07 22:29 ` David Miller
2011-04-07 22:31 ` David Miller
2011-04-07 22:31 ` David Miller
2011-04-07 22:52 ` David Miller
2011-04-07 22:52 ` David Miller
2011-04-07 23:22 ` Benjamin Herrenschmidt
2011-04-07 23:21 ` Benjamin Herrenschmidt
2011-04-07 3:26 ` [PATCH 2/5] microblaze/pci: Remove powermac originated cruft Benjamin Herrenschmidt
2011-04-07 3:26 ` Benjamin Herrenschmidt
2011-04-07 3:26 ` [PATCH 3/5] microblaze/pci: Move the remains of pci_32.c to pci-common.c Benjamin Herrenschmidt
2011-04-07 3:26 ` [PATCH 4/5] x86/devicetree: Use generic PCI <-> OF matching Benjamin Herrenschmidt
2011-04-07 10:30 ` Sebastian Andrzej Siewior
2011-04-07 3:26 ` [PATCH 5/5] pci/of: Consolidate pci_device_to_OF_node() Benjamin Herrenschmidt
2011-04-07 11:54 ` [PATCHES] Generalize PCI <-> OF node matching Michal Simek
2011-04-07 21:50 ` Benjamin Herrenschmidt
2011-04-07 22:16 ` David Miller [this message]
2011-04-07 22:30 ` Benjamin Herrenschmidt
2011-04-07 22:31 ` David Miller
2011-04-07 22:31 ` David Miller
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=20110407.151636.183068185.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benh@kernel.crashing.org \
--cc=bheglaas@google.com \
--cc=bigeasy@linuxtronix.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=tglx@linuxtronix.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).