netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: torvalds@linux-foundation.org, bryan.wu@analog.com,
	netdev <netdev@vger.kernel.org>
Subject: Re: [patch 089/181] Blackfin: on-chip ethernet MAC controller driver
Date: Sun, 06 May 2007 20:20:40 -0400	[thread overview]
Message-ID: <463E70D8.6000403@garzik.org> (raw)
In-Reply-To: <200705062150.l46LoVWQ024648@shell0.pdx.osdl.net>

akpm@linux-foundation.org wrote:
> From: "Wu, Bryan" <bryan.wu@analog.com>
> 
> This patch implements the driver necessary use the Analog Devices
> Blackfin processor's on-chip ethernet MAC controller.
> 
> Signed-off-by: Bryan Wu <bryan.wu@analog.com>
> Cc: Jeff Garzik <jeff@garzik.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  drivers/net/Kconfig    |   44 +
>  drivers/net/Makefile   |    1 
>  drivers/net/bfin_mac.c |  981 +++++++++++++++++++++++++++++++++++++++
>  drivers/net/bfin_mac.h |  147 +++++
>  4 files changed, 1173 insertions(+)

WTF?

Why are new network drivers not going to me, netdev, and/or DaveM?

Something is really broken here.  What is it?

I NAK this driver purely on the basis of lack of review.

	Jeff




       reply	other threads:[~2007-05-07  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705062150.l46LoVWQ024648@shell0.pdx.osdl.net>
2007-05-07  0:20 ` Jeff Garzik [this message]
2007-05-07  3:40   ` [patch 089/181] Blackfin: on-chip ethernet MAC controller driver Randy Dunlap
     [not found] ` <1179909013.10328.9.camel@roc-desktop>
     [not found]   ` <465405A1.5030409@garzik.org>
2007-05-23  9:16     ` Bryan Wu

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=463E70D8.6000403@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=bryan.wu@analog.com \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).