From: Grant Likely <grant.likely@secretlab.ca>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
jwboyer@linux.vnet.ibm.com, john.williams@petalogix.com,
michal.simek@petalogix.com, jtyner@cs.ucr.edu,
john.linn@xilinx.com
Subject: Re: [PATCH] [V2] Add non-Virtex5 support for LL TEMAC driver
Date: Mon, 5 Apr 2010 13:31:55 -0600 [thread overview]
Message-ID: <t2qfa686aa41004051231v40d7b456y90f14abfca9a06bf@mail.gmail.com> (raw)
In-Reply-To: <20100405.121647.91426186.davem@davemloft.net>
On Mon, Apr 5, 2010 at 1:16 PM, David Miller <davem@davemloft.net> wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
> Date: Mon, 5 Apr 2010 12:10:51 -0600
>
>> David, are you going to pick up this patch, or would you like me to?
>
> The submitter, when asked, stated that he couldn't even get
> the driver to build on microblaze against mainline.
>
> So I marked the patch "changed requested" because being able
> to build is... you know... sort of a requirement for integration.
Heh, the current driver doesn't build on microblaze either. However,
John, since you're removing the depends on PPC_DCR_NATIVE, can you
please respin the patch to make it depend on CONFIG_PPC and CONFIG_OF.
Looking at it now I see that as-is it will cause collateral damage to
allmodconfig on every other architecture.
g.
next prev parent reply other threads:[~2010-04-05 19:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 1:05 [PATCH] [V2] Add non-Virtex5 support for LL TEMAC driver John Linn
2010-03-15 8:39 ` Michal Simek
2010-03-15 13:40 ` John Linn
2010-03-15 14:39 ` Michal Simek
2010-03-15 14:51 ` John Linn
2010-03-15 14:57 ` Michal Simek
2010-03-18 0:46 ` Edgar E. Iglesias
2010-03-15 17:03 ` Stephen Neuendorffer
[not found] ` <977C41F842E66D4CB2E41332313B615009A27BCA@XSJ-EXCHVS1.xlnx.xilinx.com>
2010-03-15 17:23 ` John Linn
2010-03-17 20:02 ` Grant Likely
2010-04-05 18:10 ` Grant Likely
2010-04-05 19:16 ` David Miller
2010-04-05 19:31 ` Grant Likely [this message]
2010-04-05 19:52 ` John Linn
2010-04-05 21:28 ` John Linn
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=t2qfa686aa41004051231v40d7b456y90f14abfca9a06bf@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=davem@davemloft.net \
--cc=john.linn@xilinx.com \
--cc=john.williams@petalogix.com \
--cc=jtyner@cs.ucr.edu \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michal.simek@petalogix.com \
--cc=netdev@vger.kernel.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).