devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Murray <amurray@embedded-bits.co.uk>
Cc: Rob Herring <robherring2@gmail.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	Michal Simek <monstr@monstr.eu>,
	Grant Likely <grant.likely@linaro.org>,
	devicetree@vger.kernel.org
Subject: Re: [RFC] Architecture independent pcibios?
Date: Wed, 09 Oct 2013 07:32:55 +1100	[thread overview]
Message-ID: <1381264375.645.234.camel@pasglop> (raw)
In-Reply-To: <CAPcvp5Fvf5nkYXWviz8cKnOsMd0nOBJXrBXgMrDKCXkSP5L-Hw@mail.gmail.com>

On Tue, 2013-10-08 at 18:20 +0100, Andrew Murray wrote:
> I then refactored some of the pci_process_bridge_OF_ranges functions
> to use this parser, this was accepted by Microblaze [2] and has been
> recently acked by Ralf for MIPS but not made it upstream yet [3]. I
> think I submitted a patch for PowerPC at one point, but not sure what
> happened to that.

Probably slipped through as I was doing some other changes in that
area on powerpc and things conflicted. I can have a look at introducing
the use of your helpers again whenever I manage to get my head out of
meetings and patch monkeying for more than 5mn...

Cheers,
Ben.

> [1]
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=29b635c00f3ebcdaf7a52c4948f6d948ad3757d3
> [2]
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4f7b6de437544cd1e2e210919cb58cbe5cc3c393
> [3]
> http://www.linux-mips.org/archives/linux-mips/2013-09/msg00125.html
> 
> I'd like to get involved, but don't have any time at the moment.

  reply	other threads:[~2013-10-08 20:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131008144211.GA25231@e102652-lin.cambridge.arm.com>
     [not found] ` <20131008144211.GA25231-CibnQJhq84/ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-10-08 16:32   ` [RFC] Architecture independent pcibios? Bjorn Helgaas
2013-10-08 16:55     ` Rob Herring
2013-10-08 17:20       ` Andrew Murray
2013-10-08 20:32         ` Benjamin Herrenschmidt [this message]
2013-10-08 20:28       ` Benjamin Herrenschmidt
2013-10-09  9:09         ` Liviu Dudau
2013-10-09 10:04           ` Liviu Dudau
2013-10-09 10:37           ` Benjamin Herrenschmidt
2013-10-09 10:45             ` Liviu Dudau
2013-10-09 14:30               ` Bjorn Helgaas
2013-10-09 16:23                 ` Liviu Dudau
2013-10-15 11:48           ` Grant Likely
2013-10-08 17:13     ` Liviu Dudau
2013-10-08 18:58       ` Bjorn Helgaas
2013-10-08 20:31       ` Benjamin Herrenschmidt
2013-10-09 11:52         ` Michal Simek

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=1381264375.645.234.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Liviu.Dudau@arm.com \
    --cc=amurray@embedded-bits.co.uk \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=olof@lixom.net \
    --cc=robherring2@gmail.com \
    /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).