From: David Miller <davem@davemloft.net>
To: eilong@broadcom.com
Cc: netdev@vger.kernel.org, pl@linux.vnet.ibm.com, yanivr@broadcom.com
Subject: Re: [PATCH 00/34]bnx2x: Bug fixes
Date: Wed, 14 Jan 2009 21:36:22 -0800 (PST) [thread overview]
Message-ID: <20090114.213622.242296202.davem@davemloft.net> (raw)
In-Reply-To: <1231951356.11301.121.camel@lb-tlvb-eliezer>
From: "Eilon Greenstein" <eilong@broadcom.com>
Date: Wed, 14 Jan 2009 18:42:35 +0200
> The problem is that more and more bugs required immediate attention so
> the result is a long list of bug fixes.
You have to understand that you absolutely cannot slap me with 34 "bug
fixes" all at once after the merge window is closed.
> Please consider applying.
I've gone through patches 1 to 17 for now. Patched I didn't apply:
1) [PATCH 02/34]bnx2x: Barriers for the compiler
Need feedback on my query, if this requires a compiler barrier
it almost certainly needs cpu reordering barriers too.
2) [PATCH 05/34]bnx2x: Setting the GSO_TYPE with LRO
As discussed at length, this isn't correct and it's not the
way to fix this problem. Implement the ethtool LRO disable
and the kernel will turn it off when bridging or routing is
being used over this interface.
3) [PATCH 10/34]bnx2x: Compilation issue on IA64
This code is ugly and even in the worst case the thing to do
is unconditionally use "%llx" and cast the arg to "long long"
to kill the warning.
4) [PATCH 13/34]bnx2x: System cache alignment
This is an optimization and has no business going in outside
of the merge window.
I'll go over the rest after I send what I have now to Linus, but don't
set your expectations high, this is way too many patches to be sending
now.
next prev parent reply other threads:[~2009-01-15 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 16:42 [PATCH 00/34]bnx2x: Bug fixes Eilon Greenstein
2009-01-15 5:36 ` David Miller [this message]
2009-01-15 9:53 ` Eilon Greenstein
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=20090114.213622.242296202.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pl@linux.vnet.ibm.com \
--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