From: David Woodhouse <dwmw2@infradead.org>
To: dmitry@broadcom.com
Cc: "ben@decadent.org.uk" <ben@decadent.org.uk>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eilon Greenstein <eilong@broadcom.com>
Subject: Re: [PATCH] bnx2x: Adding FW 7.0.29.0
Date: Mon, 24 Oct 2011 16:33:17 +0200 [thread overview]
Message-ID: <1319466799.13738.108.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1319464676.6155.3.camel@lb-tlvb-dmitry>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Mon, 2011-10-24 at 15:57 +0200, Dmitry Kravkov wrote:
> On Mon, 2011-10-17 at 09:12 -0700, Dmitry Kravkov wrote:
> > On Mon, 2011-10-17 at 07:00 -0700, Dmitry Kravkov wrote:
> > > Includes fixes for the following issues:
> > > 1. (iSCSI) Arrival of un-solicited ASYNC message causes
> > > firmware to abort the connection with RST.
> > > 2. (FCoE) There is a probability that truncated FCoE packet on
> > > RX path won't get detected which might lead to FW assert.
> > > 3. (iSCSI) Arrival of target-initiated NOP-IN during intense
> > > ISCSI traffic might lead to FW assert.
> > > 4. (iSCSI) Chip hangs when in case of retransmission not aligned
> > > to 4-bytes from the beginning of iSCSI PDU.
> > > 5. (FCoE) Arrival of packets beyond task IO size can lead to crash.
> > >
>
> David, do you have estimation to handle the request? We have pending
> patch for net-next. Thanks.
Pushed to git.infradead.org; thanks. I'll work on getting the tree back
onto git.kernel.org now I'm sitting at a table with the admin...
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5818 bytes --]
prev parent reply other threads:[~2011-10-24 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1318860047-5044-1-git-send-email-dmitry@broadcom.com>
2011-10-17 16:12 ` [PATCH] bnx2x: Adding FW 7.0.29.0 Dmitry Kravkov
2011-10-24 13:57 ` Dmitry Kravkov
2011-10-24 14:33 ` David Woodhouse [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=1319466799.13738.108.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=ben@decadent.org.uk \
--cc=dmitry@broadcom.com \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.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).