From: Kevin Hilman <khilman@deeprootsystems.com>
To: Sriramakrishnan <srk@ti.com>
Cc: netdev@vger.kernel.org, davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH 0/3] TI EMAC driver : Make driver re-usable on non-davinci platforms.
Date: Wed, 18 Nov 2009 09:53:47 -0800 [thread overview]
Message-ID: <87r5rvd8ic.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1258537328-31527-1-git-send-email-srk@ti.com> (Sriramakrishnan's message of "Wed\, 18 Nov 2009 15\:12\:05 +0530")
Sriramakrishnan <srk@ti.com> writes:
> The Davinci EMAC peripheral is also available on other TI platforms -
> notably TI AM3517 SoC. The following series of patches modify the driver
> suitably to make it platform agnostic.
>
> Sriramakrishnan (3):
> TI Davinci EMAC : Re-use driver for other platforms.
> TI Davinci EMAC : add platform specific interrupt enable/disable
> logic.
> TI Davinci EMAC : Abstract Buffer address translation logic.
>
As David proposed, this should go upstream via the ARM/DaVinci route.
Can you please re-submit against current DaVinci git? This series
doesn't apply there currently.
Kevin
prev parent reply other threads:[~2009-11-18 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 9:42 [PATCH 0/3] TI EMAC driver : Make driver re-usable on non-davinci platforms Sriramakrishnan
2009-11-18 9:42 ` [PATCH 1/3] TI Davinci EMAC : Re-use driver for other platforms Sriramakrishnan
2009-11-18 9:42 ` [PATCH 2/3] TI Davinci EMAC : add platform specific interrupt enable/disable logic Sriramakrishnan
2009-11-18 9:42 ` [PATCH 3/3] TI Davinci EMAC : Abstract Buffer address translation logic Sriramakrishnan
2009-11-18 19:15 ` Troy Kisky
[not found] ` <1258537328-31527-3-git-send-email-srk-l0cyMroinI0@public.gmane.org>
2009-11-18 19:08 ` [PATCH 2/3] TI Davinci EMAC : add platform specific interrupt enable/disable logic Troy Kisky
2009-11-18 22:29 ` Kevin Hilman
2009-11-18 13:12 ` [PATCH 0/3] TI EMAC driver : Make driver re-usable on non-davinci platforms David Miller
2009-11-18 17:53 ` Kevin Hilman [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=87r5rvd8ic.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=netdev@vger.kernel.org \
--cc=srk@ti.com \
/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).