From: David Miller <davem@davemloft.net>
To: eilong@broadcom.com
Cc: netdev@vger.kernel.org, yanivr@broadcom.com, harvey.harrison@gmail.com
Subject: Re: [PATCH 00/41]bnx2x: enhancements and clean up for net-next
Date: Sun, 15 Feb 2009 23:36:09 -0800 (PST) [thread overview]
Message-ID: <20090215.233609.86653297.davem@davemloft.net> (raw)
In-Reply-To: <1234463763.1863.131.camel@lb-tlvb-eliezer>
From: "Eilon Greenstein" <eilong@broadcom.com>
Date: Thu, 12 Feb 2009 20:36:03 +0200
> Finally, an enhancement patch for the bnx2x. Due to many reasons (among
> which FW stability and chasing some bugs) it took a while to stabilize
> and the longer it took the longer the list got. So unfortunately, this
> is a long list - hopefully for the last time. I realize that sending a
> too many patches together is bad practice and I will do my best to avoid
> it in the future.
You're lucky I'm in a really good mood today :-)
> The first patch is a new FW patch. It is way too big for the mailing
> list, but I'm hoping you will get it directly to your mailbox. This
> patch has very little review value since it is simply the new FW blob,
> FW header file renames and the mandatory driver renames to accommodate
> it.
>
> Please consider applying to net-next.
Ok, everything is applied to net-next-2.6 and pushed out to kernel.org
Please followup with patches for Ben Hutchings's feedback, as you
promised you would.
Thank you.
prev parent reply other threads:[~2009-02-16 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 18:36 [PATCH 00/41]bnx2x: enhancements and clean up for net-next Eilon Greenstein
2009-02-16 7:36 ` David Miller [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=20090215.233609.86653297.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=harvey.harrison@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yanivr@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