From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Saurav Kashyap <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 v4 0/9] qed/qedf: Firmware recovery, bw update and misc fixes.
Date: Fri, 17 Apr 2020 17:57:42 -0400 [thread overview]
Message-ID: <yq1eesln5bd.fsf@oracle.com> (raw)
In-Reply-To: <20200416084314.18851-1-skashyap@marvell.com> (Saurav Kashyap's message of "Thu, 16 Apr 2020 01:43:05 -0700")
Saurav,
> Kindly apply this series to scsi tree at your earliest convenience.
Fixed a few things, including a sparse warning and the error message
pointed out by Sergei. Applied to 5.8/scsi-queue, thank you!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-04-17 21:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 8:43 [PATCH v4 0/9] qed/qedf: Firmware recovery, bw update and misc fixes Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 1/9] qedf: Keep track of num of pending flogi Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 2/9] qedf: Increase the upper limit of retry delay Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 3/9] qedf: Acquire rport_lock for resetting the delay_timestamp Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 4/9] qedf: Honor status qualifier in FCP_RSP per spec Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 5/9] qed: Send BW update notifications to the protocol drivers Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 6/9] qedf: Implement callback for bw_update Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 7/9] qedf: Add schedule recovery handler Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 8/9] qedf: Fix crash when MFW calls for protocol stats while function is still probing Saurav Kashyap
2020-04-16 8:43 ` [PATCH v4 9/9] qedf: Get dev info after updating the params Saurav Kashyap
2020-04-16 9:41 ` Sergei Shtylyov
2020-04-17 21:57 ` Martin K. Petersen [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=yq1eesln5bd.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=jhasan@marvell.com \
--cc=linux-scsi@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.