From: David Miller <davem@davemloft.net>
To: skashyap@marvell.com
Cc: martin.petersen@oracle.com,
GR-QLogic-Storage-Upstream@marvell.com,
linux-scsi@vger.kernel.org, jhasan@marvell.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/8] qed/qedf: Firmware recovery, bw update and misc fixes.
Date: Mon, 30 Mar 2020 10:12:02 -0700 (PDT) [thread overview]
Message-ID: <20200330.101202.660829992934953878.davem@davemloft.net> (raw)
In-Reply-To: <20200330063034.27309-1-skashyap@marvell.com>
You add the new qed_bw_update() function but nothing invokes it.
Remove this from the patch series until you are submitting changes
that actually use the function.
next prev parent reply other threads:[~2020-03-30 17:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 6:30 [PATCH v2 0/8] qed/qedf: Firmware recovery, bw update and misc fixes Saurav Kashyap
2020-03-30 6:30 ` [PATCH v2 1/8] qedf: Keep track of num of pending flogi Saurav Kashyap
2020-03-30 6:30 ` [PATCH v2 2/8] qedf: Fix for the deviations from the SAM-4 spec Saurav Kashyap
2020-03-30 6:30 ` [PATCH v2 3/8] qed: Send BW update notifications to the protocol drivers Saurav Kashyap
2020-03-30 6:30 ` [PATCH v2 4/8] qedf: Implement callback for bw_update Saurav Kashyap
2020-03-30 6:30 ` [PATCH v2 5/8] qedf: Add schedule recovery handler Saurav Kashyap
2020-03-30 6:30 ` [PATCH v2 6/8] qedf: Fix crash when MFW calls for protocol stats while function is still probing Saurav Kashyap
2020-03-30 6:30 ` [PATCH v2 7/8] qedf: Get dev info after updating the params Saurav Kashyap
2020-03-30 6:30 ` [PATCH v2 8/8] qedf: Update the driver version to 8.42.3.5 Saurav Kashyap
2020-03-30 7:32 ` Leon Romanovsky
2020-03-30 11:04 ` [EXT] " Saurav Kashyap
2020-03-30 7:33 ` [PATCH v2 0/8] qed/qedf: Firmware recovery, bw update and misc fixes Leon Romanovsky
2020-03-30 17:12 ` David Miller [this message]
2020-03-31 4:12 ` [EXT] " Saurav Kashyap
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=20200330.101202.660829992934953878.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=jhasan@marvell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=skashyap@marvell.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;
as well as URLs for NNTP newsgroup(s).