Netdev List
 help / color / mirror / Atom feed
From: "Eilon Greenstein" <eilong@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Yaniv Rosner" <yaniv.rosner@broadcom.com>,
	"Vladislav Zolotarov" <vladz@broadcom.com>,
	"Yitchak Gertner" <yitchak.gertner@broadcom.com>,
	"Benjamin Li" <benli@broadcom.com>
Subject: Re: [net-next 00/36] bnx2x patch series
Date: Thu, 13 Aug 2009 09:35:25 +0300	[thread overview]
Message-ID: <1250145325.27379.190.camel@lb-tlvb-eilong> (raw)
In-Reply-To: <20090812.230912.102740872.davem@davemloft.net>

On Wed, 2009-08-12 at 23:09 -0700, David Miller wrote:
> From: "Eilon Greenstein" <eilong@broadcom.com>
> Date: Wed, 12 Aug 2009 21:19:22 +0300
> 
> > Here is a patch series for the bnx2x. This patch series also replace the
> > FW, so
> > it contains two big blobs - the new fw and the removal of the old one.
> > Those
> > patches do not contain anything but the ihex - the actually change to
> > the driver
> > is in patch number 2 which is small enough to fit the mailing list.
> > 
> > For those who wish to see all the patches, including the ihex, I also
> > updated
> > http://linux.broadcom.com/eilong/ to contain this patch series.
> > 
> > Please consider applying to net-next.
> 
> I've applied it all, but sincerely this is absolutely the last
> time I'm taking in a patch bomb for a Broadcom ethernet driver.
> 
> If it's new stuff, keep it to ~10 patches.
> 
> If it's bug fixes outside of the merge window, keep it at
> 2 or 3 patches.
> 
> Post them very near to when you write them, so people have a chance of
> actually reviewing your work (I guarentee I am the only non-Broadcom
> person who looked over all 36 patches, or who ever will).
> 
> "Early and often" as it were...
> 
Will do!

Thanks,
Eilon



      reply	other threads:[~2009-08-13  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 18:19 [net-next 00/36] bnx2x patch series Eilon Greenstein
2009-08-12 21:50 ` David Miller
2009-08-13  6:09 ` David Miller
2009-08-13  6:35   ` Eilon Greenstein [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=1250145325.27379.190.camel@lb-tlvb-eilong \
    --to=eilong@broadcom.com \
    --cc=benli@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=vladz@broadcom.com \
    --cc=yaniv.rosner@broadcom.com \
    --cc=yitchak.gertner@broadcom.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