From: Sascha Hauer <s.hauer@pengutronix.de>
To: David Miller <davem@davemloft.net>
Cc: gerg@snapgear.com, netdev@vger.kernel.org, fred.rodo@gmail.com
Subject: Re: FEC Patches
Date: Thu, 29 Jan 2009 10:03:45 +0100 [thread overview]
Message-ID: <20090129090345.GG8446@pengutronix.de> (raw)
In-Reply-To: <20090128.123110.120011613.davem@davemloft.net>
On Wed, Jan 28, 2009 at 12:31:10PM -0800, David Miller wrote:
> From: Sascha Hauer <s.hauer@pengutronix.de>
> Date: Wed, 28 Jan 2009 19:53:39 +0100
>
> > Hi Greg,
> >
> > On Wed, Jan 28, 2009 at 05:37:21PM +1000, Greg Ungerer wrote:
> > > Hi Sascha,
> > >
> > > Sascha Hauer wrote:
> > >> Sorry guys, sending this again. Of course I'm not 'y', just playing
> > >> git-send-email:
> > >>
> > >> Who should the emails appear to be from? [Sascha Hauer <s.hauer@pengutronix.de>] y[es]
> > >> Emails will be sent from: y
> > >>
> > >>
> > >> These patches are an updated version from the ones I posted some time ago.
> > >> They give the FEC ethernet driver a facelift and turn it into a
> > >> platform_device driver. The Coldfire cores are still supported through
> > >> legacy ifdefs. The platform driver support has been tested on a
> > >> Freescale i.MX27 SoC.
> > >
> > > Outside of the one patch I commented on the series applies, runs and
> > > seems to work OK on the ColdFire parts I tried it on.
> >
> > Thanks for testing the patches. I'll add the change you mentioned.
> > So this means I can add your Acked-by and send a pull request, well to
> > whom? David Miller, Jeff Garzik?
>
> Just send it to netdev and CC: me.
Done, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2009-01-29 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 10:39 FEC Patches Sascha Hauer
2009-01-27 10:39 ` [PATCH] fec: remove unused #else branches Sascha Hauer
2009-01-27 10:39 ` [PATCH] fec: remove empty functions Sascha Hauer
2009-01-27 10:39 ` [PATCH] fec: use linux/*.h instead of asm/*.h Sascha Hauer
2009-01-27 10:39 ` [PATCH] fec: do not use memcpy on physical addresses Sascha Hauer
2009-01-27 10:40 ` [PATCH] fec: use dma_alloc_coherent for descriptor ring Sascha Hauer
2009-01-27 10:40 ` [PATCH] fec: Fix KS8721BL_ICSR phy register offset Sascha Hauer
2009-01-27 10:40 ` [PATCH] fec: replace flush_dcache_range with dma_sync_single Sascha Hauer
2009-01-27 10:40 ` [PATCH] fec: Add support for Freescale MX27 Sascha Hauer
2009-01-27 10:40 ` [PATCH] FEC: Turn FEC driver into platform device driver Sascha Hauer
2009-01-28 7:36 ` Greg Ungerer
2009-01-28 7:37 ` FEC Patches Greg Ungerer
2009-01-28 18:53 ` Sascha Hauer
2009-01-28 20:31 ` David Miller
2009-01-29 9:03 ` Sascha Hauer [this message]
2009-01-28 23:46 ` Greg Ungerer
-- strict thread matches above, loose matches on Subject: below --
2009-01-29 9:03 FEC patches Sascha Hauer
2009-01-30 0:04 ` David Miller
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=20090129090345.GG8446@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=davem@davemloft.net \
--cc=fred.rodo@gmail.com \
--cc=gerg@snapgear.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).