Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Murray <amurray@embedded-bits.co.uk>
Cc: linux-mips@linux-mips.org
Subject: Re: Status of mips 'of/pci: Use of_pci_range_parser' patch
Date: Wed, 18 Sep 2013 14:16:59 +0200	[thread overview]
Message-ID: <20130918121658.GB23804@linux-mips.org> (raw)
In-Reply-To: <CAPcvp5HYxPeBp9HAQ4hNFrpWMc_ADkfbvZnYeWXvOaACt5VSAg@mail.gmail.com>

On Fri, Aug 09, 2013 at 11:43:40AM +0100, Andrew Murray wrote:

> Hi Ralf,
> 
> What is the status of this patch?  http://patchwork.linux-mips.org/patch/5625/
> 
> I'm not sure if you've missed this. Are you able to apply this to your tree?

I didn't get around to apply it in time so it had to wait for another
release.  Sorry about that.  But I finally queued it up for 2.13.

Thanks!

  Ralf

      reply	other threads:[~2013-09-18 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 10:43 Status of mips 'of/pci: Use of_pci_range_parser' patch Andrew Murray
2013-09-18 12:16 ` Ralf Baechle [this message]

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=20130918121658.GB23804@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=amurray@embedded-bits.co.uk \
    --cc=linux-mips@linux-mips.org \
    /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