netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Linsys Contractor Mithlesh Thukral <mithlesh@netxen.com>
Cc: netdev@vger.kernel.org, netxenproj@linsyssoft.com, rob@netxen.com
Subject: Re: [PATCH 3/3] NetXen: Make driver use multi PCI functions
Date: Fri, 02 Mar 2007 20:05:16 -0500	[thread overview]
Message-ID: <45E8C9CC.7030005@garzik.org> (raw)
In-Reply-To: <200702281319.l1SDJ2FV004424@dut39.unminc.com>

Linsys Contractor Mithlesh Thukral wrote:
> NetXen: Make driver use multi PCI functions.
> 
> Signed-off by: Mithlesh Thukral <mithlesh@netxen.com>
> 
> ---
> 
>  netxen_nic.h          |  126 +++++-------
>  netxen_nic_ethtool.c  |   80 +++----
>  netxen_nic_hdr.h      |    8 
>  netxen_nic_hw.c       |  213 +++++++++++++++-----
>  netxen_nic_hw.h       |   18 -
>  netxen_nic_init.c     |  115 +++-------
>  netxen_nic_isr.c      |   80 +++----
>  netxen_nic_main.c     |  523 +++++++++++++++++++++++++-------------------------
>  netxen_nic_niu.c      |   27 +-
>  netxen_nic_phan_reg.h |  125 -----------
>  10 files changed, 631 insertions(+), 684 deletions(-)

all three patches in this patchset contained nothing but one-line 
summaries of the changes included in them, and are overall very poorly 
and vaguely described.

This patch is far too big, with far too little description and 
justification to go along with it.

If you are not going to make the effort to write a paragraph or two 
describing such huge changes, then I'm not going to make the effort to 
review and apply it.  NAK.



  reply	other threads:[~2007-03-03  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 13:19 [PATCH 3/3] NetXen: Make driver use multi PCI functions Linsys Contractor Mithlesh Thukral
2007-03-03  1:05 ` Jeff Garzik [this message]
2007-03-05 12:57   ` Mithlesh Thukral

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=45E8C9CC.7030005@garzik.org \
    --to=jeff@garzik.org \
    --cc=mithlesh@netxen.com \
    --cc=netdev@vger.kernel.org \
    --cc=netxenproj@linsyssoft.com \
    --cc=rob@netxen.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).