From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@cavium.com
Cc: netdev@vger.kernel.org, linux-scsi@vger.kernel.org,
Chad.Dupuis@cavium.com, Ram.Amrani@cavium.com,
Tomer.Tayar@cavium.com, Manish.Rangankar@cavium.com
Subject: Re: [PATCH net-next] qed: Utilize FW 8.20.0.0
Date: Thu, 18 May 2017 10:43:00 -0400 (EDT) [thread overview]
Message-ID: <20170518.104300.795177460216894201.davem@davemloft.net> (raw)
In-Reply-To: <20170518.103428.1194147893495615244.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Thu, 18 May 2017 10:34:28 -0400 (EDT)
> From: Yuval Mintz <Yuval.Mintz@cavium.com>
> Date: Wed, 17 May 2017 22:38:40 +0300
>
>> This pushes qed [and as result, all qed* drivers] into using 8.20.0.0
>> firmware. The changes are mostly contained in qed with minor changes
>> to qedi due to some HSI changes.
>>
>> Content-wise, the firmware contains fixes to various issues exposed
>> since the release of the previous firmware, including:
>> - Corrects iSCSI fast retransmit when data digest is enabled.
>> - Stop draining packets when receiving several consecutive PFCs.
>> - Prevent possible assertion when consecutively opening/closing
>> many connections.
>> - Prevent possible assertion due to too long BDQ fetch time.
>>
>> In addition, the new firmware would allow us to later add iWARP support
>> in qed and qedr.
>>
>> Signed-off-by: Chad Dupuis <Chad.Dupuis@cavium.com>
>> Signed-off-by: Ram Amrani <Ram.Amrani@cavium.com>
>> Signed-off-by: Tomer Tayar <Tomer.Tayar@cavium.com>
>> Signed-off-by: Manish Rangankar <Manish.Rangankar@cavium.com>
>> Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com>
>
> Applied.
Actually I had to revert. Please look at the compiler output before
submitting changes:
drivers/net/ethernet/qlogic/qed/qed_debug.c: In function ‘qed_grc_dump’:
drivers/net/ethernet/qlogic/qed/qed_debug.c:2425:6: warning: ‘addr’ may be used uninitialized in this function [-Wmaybe-uninitialized]
u32 byte_addr = DWORDS_TO_BYTES(addr), offset = 0, i;
^
drivers/net/ethernet/qlogic/qed/qed_debug.c:3534:7: note: ‘addr’ was declared here
u32 addr, size = RSS_REG_RSS_RAM_DATA_SIZE;
^
'addr' is never, ever, assigned a value, yet it is passed into a function as an
argument.
next prev parent reply other threads:[~2017-05-18 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 19:38 [PATCH net-next] qed: Utilize FW 8.20.0.0 Yuval Mintz
2017-05-18 14:34 ` David Miller
2017-05-18 14:43 ` David Miller [this message]
2017-05-18 15:28 ` Mintz, Yuval
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=20170518.104300.795177460216894201.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Chad.Dupuis@cavium.com \
--cc=Manish.Rangankar@cavium.com \
--cc=Ram.Amrani@cavium.com \
--cc=Tomer.Tayar@cavium.com \
--cc=Yuval.Mintz@cavium.com \
--cc=linux-scsi@vger.kernel.org \
--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