From: Rob Herring <robherring2@gmail.com>
To: John Crispin <blogic@openwrt.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-mips@linux-mips.org, linux-pci@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Ralf Baechle <ralf@linux-mips.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] OF: PCI: const usage needed by MIPS
Date: Thu, 17 May 2012 17:14:58 -0500 [thread overview]
Message-ID: <4FB57862.5000700@gmail.com> (raw)
In-Reply-To: <4FADFB39.6010100@openwrt.org>
On 05/12/2012 12:55 AM, John Crispin wrote:
>
>> I compiled alpha, ia64, mips, parisc, powerpc, sh, sparc, and x86 and
>> didn't see any issues related to this patch. There might still be
>> something, but I'm willing to help work through them or revert this
>> if it turns out to be a problem. I'm still assuming that Grant will
>> handle this.
>>
>> Bjorn
> Hi Grant,
>
> Is this patch ok with you ? If so would you mind if Ralf takes this via
> his tree ? (this would avoid merge order problems)
>
This looks fine to me and merging thru Ralf's tree is fine.
Acked-by: Rob Herring <rob.herring@calxeda.com>
Rob
> Thanks,
> John
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
prev parent reply other threads:[~2012-05-18 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 17:46 [PATCH] OF: PCI: const usage needed by MIPS John Crispin
2012-04-30 17:54 ` David Daney
2012-05-01 13:28 ` John Crispin
2012-05-04 0:30 ` Bjorn Helgaas
2012-05-04 1:17 ` David Daney
2012-05-04 10:55 ` John Crispin
2012-05-07 15:11 ` Bjorn Helgaas
2012-05-08 10:35 ` John Crispin
2012-05-12 5:55 ` John Crispin
2012-05-17 22:14 ` Rob Herring [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=4FB57862.5000700@gmail.com \
--to=robherring2@gmail.com \
--cc=bhelgaas@google.com \
--cc=blogic@openwrt.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-mips@linux-mips.org \
--cc=linux-pci@vger.kernel.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.