From: David Miller <davem@davemloft.net>
To: grant.likely@secretlab.ca
Cc: eric.dumazet@gmail.com, michal.simek@petalogix.com,
netdev@vger.kernel.org, jtyner@cs.ucr.edu,
linuxppc-dev@ozlabs.org, john.linn@xilinx.com,
john.williams@petalogix.com
Subject: Re: [PATCH 2/2] [V5] Add non-Virtex5 support for LL TEMAC driver
Date: Tue, 13 Apr 2010 01:34:03 -0700 (PDT) [thread overview]
Message-ID: <20100413.013403.184052247.davem@davemloft.net> (raw)
In-Reply-To: <x2sfa686aa41004091110l87cd2234rc68906080fc4fe03@mail.gmail.com>
From: Grant Likely <grant.likely@secretlab.ca>
Date: Fri, 9 Apr 2010 12:10:21 -0600
> On Thu, Apr 8, 2010 at 11:08 AM, John Linn <john.linn@xilinx.com> wrote:
>> This patch adds support for using the LL TEMAC Ethernet driver on
>> non-Virtex 5 platforms by adding support for accessing the Soft DMA
>> registers as if they were memory mapped instead of solely through the
>> DCR's (available on the Virtex 5).
>>
>> The patch also updates the driver so that it runs on the MicroBlaze.
>> The changes were tested on the PowerPC 440, PowerPC 405, and the
>> MicroBlaze platforms.
>>
>> Signed-off-by: John Tyner <jtyner@cs.ucr.edu>
>> Signed-off-by: John Linn <john.linn@xilinx.com>
>
> Picked up and build tested both patches on 405, 440, 60x and ppc64.
> No build problems found either built-in or as a module.
>
> for both:
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
Ok, both applied to net-next-2.6, thanks everyone for sorting this
out.
next prev parent reply other threads:[~2010-04-13 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1270746482-29914-1-git-send-email-john.linn@xilinx.com>
2010-04-08 17:08 ` [PATCH 2/2] [V5] Add non-Virtex5 support for LL TEMAC driver John Linn
2010-04-09 18:10 ` Grant Likely
2010-04-13 8:34 ` David Miller [this message]
2010-04-13 14:43 ` John Linn
2010-04-11 13:16 ` Michal Simek
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=20100413.013403.184052247.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=john.linn@xilinx.com \
--cc=john.williams@petalogix.com \
--cc=jtyner@cs.ucr.edu \
--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).