From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Einon <mark.einon@gmail.com>
Cc: davem@davemloft.net, sfr@canb.auug.org.au,
devel@driverdev.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH linux-next] et131x: Promote staging et131x driver to drivers/net
Date: Fri, 18 Jan 2013 14:57:06 -0800 [thread overview]
Message-ID: <20130118225706.GA22140@kroah.com> (raw)
In-Reply-To: <1358541648-29922-1-git-send-email-mark.einon@gmail.com>
On Fri, Jan 18, 2013 at 08:40:47PM +0000, Mark Einon wrote:
> This patch moves the et131x gigabit ethernet driver from drivers/staging
> to drivers/net/ethernet/agere.
>
> All the existing issues noted for this driver have been resolved, apart
> from one performance issue where some fragmented packets suffer from
> frame receive errors. As I've only tested the code on one piece of
> hardware to date, it would be useful to get feedback on this issue from
> any other users of the device (my device has been stepped on several times
> now, and is known to need a few wiggles before starting up correctly).
>
> Signed-off-by: Mark Einon <mark.einon@gmail.com>
No objection from me for this. It's up to the network driver
maintainers if this is ok or not.
greg k-h
next prev parent reply other threads:[~2013-01-18 22:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 20:40 [RFC PATCH linux-next] et131x: Promote staging et131x driver to drivers/net Mark Einon
2013-01-18 22:57 ` Greg KH [this message]
2013-01-19 11:03 ` Dan Carpenter
2013-01-19 11:48 ` [PATCH] staging: et131x: Fix all sparse warnings Mark Einon
2013-01-21 23:44 ` [RFC PATCH linux-next] et131x: Promote staging et131x driver to drivers/net Mark Einon
2013-01-22 6:20 ` Dan Carpenter
2013-01-23 10:10 ` [RFC PATCH v2 " Mark Einon
2013-01-23 10:31 ` Dan Carpenter
2013-01-23 11:31 ` Mark Einon
2013-01-23 12:45 ` [RFC PATCH v3 " Mark Einon
2013-01-23 14:32 ` Greg KH
2013-01-23 14:51 ` Mark Einon
2013-01-23 16:24 ` [RFC PATCH v4 " Mark Einon
2013-01-29 4:10 ` David Miller
2013-01-29 12:47 ` Mark Einon
2014-09-22 21:28 [RFC PATCH " Mark Einon
2014-09-22 23:56 ` Angus Gibson
2014-09-23 9:51 ` Mark Einon
2014-09-23 9:51 ` Mark Einon
2014-09-23 1:57 ` Joe Perches
2014-09-23 9:50 ` Mark Einon
2014-09-23 9:50 ` Mark Einon
2014-09-23 7:22 ` Tobias Klauser
2014-09-23 7:22 ` Tobias Klauser
2014-09-23 9:46 ` Mark Einon
2014-09-23 9:46 ` Mark Einon
2014-09-23 10:01 ` Tobias Klauser
2014-09-23 10:01 ` Tobias Klauser
2014-09-23 11:06 ` Mark Einon
2014-09-23 11:06 ` Mark Einon
2014-09-23 19:02 ` Francois Romieu
2014-09-23 19:17 ` Joe Perches
2014-09-23 20:07 ` Francois Romieu
2014-09-23 20:07 ` Francois Romieu
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=20130118225706.GA22140@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.einon@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.