From: Nilesh Javali <njavali@marvell.com>
To: <martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>,
<GR-QLogic-Storage-Upstream@marvell.com>, <bhazarika@marvell.com>,
<agurumurthy@marvell.com>
Subject: [PATCH v2 0/7] qla2xxx driver features
Date: Fri, 26 Aug 2022 03:25:52 -0700 [thread overview]
Message-ID: <20220826102559.17474-1-njavali@marvell.com> (raw)
Martin,
Please apply the qla2xxx driver features to the scsi tree
at your earliest convenience.
v2:
- Revert and incorporate fix based on review comments for,
"qla2xxx: Fix response queue handler reading stale packets"
- Incorporate review comments for adding enhancement to driver tracing
infrastucture.
Thanks,
Nilesh
Anil Gurumurthy (1):
qla2xxx: Add NVMe parameters support in Auxiliary Image Status
Arun Easi (4):
Revert "scsi: qla2xxx: Fix response queue handler reading stale
packets"
qla2xxx: Fix response queue handler reading stale packets
qla2xxx: Add debugfs create/delete helpers
qla2xxx: Enhance driver tracing with separate tunable and more
Nilesh Javali (2):
qla2xxx: define static symbols
qla2xxx: Update version to 10.02.07.900-k
drivers/scsi/qla2xxx/qla_bsg.c | 8 ++-
drivers/scsi/qla2xxx/qla_bsg.h | 3 +-
drivers/scsi/qla2xxx/qla_dbg.c | 50 +++++++++++-----
drivers/scsi/qla2xxx/qla_dbg.h | 43 ++++++++++++++
drivers/scsi/qla2xxx/qla_def.h | 7 +++
drivers/scsi/qla2xxx/qla_dfs.c | 93 ++++++++++++++++++++++++++++++
drivers/scsi/qla2xxx/qla_fw.h | 3 +
drivers/scsi/qla2xxx/qla_gbl.h | 3 +-
drivers/scsi/qla2xxx/qla_init.c | 8 ++-
drivers/scsi/qla2xxx/qla_isr.c | 22 +++----
drivers/scsi/qla2xxx/qla_os.c | 47 +++++++++++----
drivers/scsi/qla2xxx/qla_version.h | 4 +-
12 files changed, 242 insertions(+), 49 deletions(-)
base-commit: d957e7ffb2c72410bcc1a514153a46719255a5da
--
2.19.0.rc0
next reply other threads:[~2022-08-26 10:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 10:25 Nilesh Javali [this message]
2022-08-26 10:25 ` [PATCH v2 1/7] Revert "scsi: qla2xxx: Fix response queue handler reading stale packets" Nilesh Javali
2022-08-29 16:09 ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 2/7] qla2xxx: Fix response queue handler reading stale packets Nilesh Javali
2022-08-29 16:10 ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 3/7] qla2xxx: Add debugfs create/delete helpers Nilesh Javali
2022-08-29 16:10 ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 4/7] qla2xxx: Add NVMe parameters support in Auxiliary Image Status Nilesh Javali
2022-08-29 16:15 ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 5/7] qla2xxx: Enhance driver tracing with separate tunable and more Nilesh Javali
2022-08-29 16:24 ` Himanshu Madhani
2022-08-29 16:59 ` Arun Easi
2022-08-29 19:25 ` Himanshu Madhani
2022-08-30 7:55 ` Daniel Wagner
2022-09-01 13:41 ` Steven Rostedt
2022-08-30 8:07 ` Daniel Wagner
2022-09-19 22:01 ` Guenter Roeck
2022-09-19 23:15 ` Arun Easi
2022-08-26 10:25 ` [PATCH v2 6/7] qla2xxx: define static symbols Nilesh Javali
2022-08-29 16:25 ` Himanshu Madhani
2022-08-26 10:25 ` [PATCH v2 7/7] qla2xxx: Update version to 10.02.07.900-k Nilesh Javali
2022-08-29 16:26 ` Himanshu Madhani
2022-09-01 4:31 ` [PATCH v2 0/7] qla2xxx driver features Martin K. Petersen
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=20220826102559.17474-1-njavali@marvell.com \
--to=njavali@marvell.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=agurumurthy@marvell.com \
--cc=bhazarika@marvell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).