From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCHv2 0/4] Xilinx Virtex support for arch/powerpc
Date: Sun, 30 Sep 2007 21:46:15 -0500 [thread overview]
Message-ID: <1191206775.10089.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20070930221613.583.252.stgit@trillian.cg.shawcable.net>
On Sun, 2007-09-30 at 16:20 -0600, Grant Likely wrote:
> 2nd version of Xilinx Virtex patches. I've addressed all the comments
> that I've received so far. This series is just the arch/powerpc support
> code. I'll send the device driver changes in a seperate series for
> each driver.
Overall looks pretty darn good. You dropped the patch to add you as the
Xilinx maintainer. Oversight?
Also, the support seems fairly generic but I don't see any ml300.dts or
ml4xx.dts files. And the Kconfig files don't select WANT_DEVICE_TREE.
Are those patches coming later, or do these boards really not need a DTS
file?
josh
next prev parent reply other threads:[~2007-10-01 2:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 22:20 [PATCHv2 0/4] Xilinx Virtex support for arch/powerpc Grant Likely
2007-09-30 22:20 ` [PATCHv2 1/4] Virtex: Add uartlite bootwrapper driver Grant Likely
2007-09-30 22:20 ` [PATCHv2 2/4] Virtex: Add Kconfig macros for Xilinx Virtex board support Grant Likely
2007-09-30 22:20 ` [PATCHv2 3/4] Virtex: add xilinx interrupt controller driver Grant Likely
2007-10-01 15:08 ` Stephen Rothwell
2007-10-01 15:16 ` Grant Likely
2007-09-30 22:20 ` [PATCHv2 4/4] Virtex: Add generic Xilinx Virtex board support Grant Likely
2007-10-01 15:06 ` Stephen Rothwell
2007-10-01 15:15 ` Grant Likely
2007-10-01 2:46 ` Josh Boyer [this message]
2007-10-01 3:44 ` [PATCHv2 0/4] Xilinx Virtex support for arch/powerpc Grant Likely
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=1191206775.10089.10.camel@localhost.localdomain \
--to=jwboyer@linux.vnet.ibm.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).