From: Karan Tilak Kumar <kartilak@cisco.com>
To: sebaddel@cisco.com
Cc: arulponn@cisco.com, djhawar@cisco.com, gcboffa@cisco.com,
mkai2@cisco.com, satishkh@cisco.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Karan Tilak Kumar <kartilak@cisco.com>
Subject: [PATCH v4 13/13] scsi: fnic: Increment driver version
Date: Wed, 29 Nov 2023 18:34:02 -0800 [thread overview]
Message-ID: <20231130023402.802282-14-kartilak@cisco.com> (raw)
In-Reply-To: <20231130023402.802282-1-kartilak@cisco.com>
Changes between v2 and v3:
Incorporate the following review comments from Hannes:
Create a separate patch to increment driver version.
Increment driver version number to 1.7.0.0.
Reviewed-by: Sesidhar Baddela <sebaddel@cisco.com>
Reviewed-by: Arulprabhu Ponnusamy <arulponn@cisco.com>
Signed-off-by: Karan Tilak Kumar <kartilak@cisco.com>
---
drivers/scsi/fnic/fnic.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/fnic/fnic.h b/drivers/scsi/fnic/fnic.h
index c4edbd7dfc25..7241aebf79d6 100644
--- a/drivers/scsi/fnic/fnic.h
+++ b/drivers/scsi/fnic/fnic.h
@@ -27,7 +27,7 @@
#define DRV_NAME "fnic"
#define DRV_DESCRIPTION "Cisco FCoE HBA Driver"
-#define DRV_VERSION "1.6.0.56"
+#define DRV_VERSION "1.7.0.0"
#define PFX DRV_NAME ": "
#define DFX DRV_NAME "%d: "
--
2.31.1
next prev parent reply other threads:[~2023-11-30 2:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 2:33 [PATCH v4 00/13] Introduce support for multiqueue (MQ) in fnic Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 01/13] scsi: fnic: Modify definitions to sync with VIC firmware Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 02/13] scsi: fnic: Add and use fnic number Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 03/13] scsi: fnic: Add and improve log messages Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 04/13] scsi: fnic: Rename wq_copy to hw_copy_wq Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 05/13] scsi: fnic: Get copy workqueue count and interrupt mode from config Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 06/13] scsi: fnic: Refactor and redefine fnic.h for multiqueue Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 07/13] scsi: fnic: Modify ISRs to support multiqueue(MQ) Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 08/13] scsi: fnic: Define stats to track multiqueue (MQ) IOs Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 09/13] scsi: fnic: Remove usage of host_lock Karan Tilak Kumar
2023-11-30 2:33 ` [PATCH v4 10/13] scsi: fnic: Add support for multiqueue (MQ) in fnic_main.c Karan Tilak Kumar
2023-11-30 2:34 ` [PATCH v4 11/13] scsi: fnic: Add support for multiqueue (MQ) in fnic driver Karan Tilak Kumar
2023-11-30 2:34 ` [PATCH v4 12/13] scsi: fnic: Improve logs and add support for multiqueue (MQ) Karan Tilak Kumar
2023-11-30 2:34 ` Karan Tilak Kumar [this message]
2023-12-06 3:10 ` [PATCH v4 00/13] Introduce support for multiqueue (MQ) in fnic Martin K. Petersen
2023-12-06 3:53 ` Karan Tilak Kumar (kartilak)
2023-12-08 18:03 ` Martin K. Petersen
2023-12-08 19:20 ` Karan Tilak Kumar (kartilak)
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=20231130023402.802282-14-kartilak@cisco.com \
--to=kartilak@cisco.com \
--cc=arulponn@cisco.com \
--cc=djhawar@cisco.com \
--cc=gcboffa@cisco.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mkai2@cisco.com \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.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