From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Murray <Andrew.Murray@arm.com>,
Michal Simek <monstr@monstr.eu>,
microblaze-uclinux@itee.uq.edu.au, linux-mips@linux-mips.org,
John Crispin <blogic@openwrt.org>,
David Daney <ddaney@caviumnetworks.com>
Subject: of_pci_range_parser patch series
Date: Thu, 27 Jun 2013 10:54:14 +0200 [thread overview]
Message-ID: <20130627085414.GE20848@linux-mips.org> (raw)
Andrew,
I noticed that [1] is now in -next but not the MIPS patch [2], not the
MicroBlaze patch [3]. What is the reason for that? If it's only the
lack of an ack, here's mine for the MIPS version:
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Thanks,
Ralf
[1] http://patchwork.linux-mips.org/patch/5218/
[2] http://patchwork.linux-mips.org/patch/5217/
[3] http://patchwork.linux-mips.org/patch/5216/
next reply other threads:[~2013-06-27 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 8:54 Ralf Baechle [this message]
[not found] <BF39C5705592B0469C55326EC158C01A80307EBE26@GEORGE.Emea.Arm.com>
2013-07-05 13:29 ` of_pci_range_parser patch series Andrew Murray
2013-07-05 17:19 ` Jason Cooper
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=20130627085414.GE20848@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Andrew.Murray@arm.com \
--cc=blogic@openwrt.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
/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