From: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
To: martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, sathya.prakash@broadcom.com,
suganath-prabu.subramani@broadcom.com,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Subject: [PATCH v1 14/14] mpt3sas: Bump driver version to 35.101.00.00
Date: Tue, 27 Oct 2020 18:38:47 +0530 [thread overview]
Message-ID: <20201027130847.9962-15-sreekanth.reddy@broadcom.com> (raw)
In-Reply-To: <20201027130847.9962-1-sreekanth.reddy@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Bump mpt3sas driver version to 35.101.00.00
Signed-off-by: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
---
v1:
No change.
drivers/scsi/mpt3sas/mpt3sas_base.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/mpt3sas/mpt3sas_base.h b/drivers/scsi/mpt3sas/mpt3sas_base.h
index badd823..7dab579 100644
--- a/drivers/scsi/mpt3sas/mpt3sas_base.h
+++ b/drivers/scsi/mpt3sas/mpt3sas_base.h
@@ -76,9 +76,9 @@
#define MPT3SAS_DRIVER_NAME "mpt3sas"
#define MPT3SAS_AUTHOR "Avago Technologies <MPT-FusionLinux.pdl@avagotech.com>"
#define MPT3SAS_DESCRIPTION "LSI MPT Fusion SAS 3.0 Device Driver"
-#define MPT3SAS_DRIVER_VERSION "35.100.00.00"
+#define MPT3SAS_DRIVER_VERSION "35.101.00.00"
#define MPT3SAS_MAJOR_VERSION 35
-#define MPT3SAS_MINOR_VERSION 100
+#define MPT3SAS_MINOR_VERSION 101
#define MPT3SAS_BUILD_VERSION 0
#define MPT3SAS_RELEASE_VERSION 00
--
2.18.4
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4175 bytes --]
next prev parent reply other threads:[~2020-10-27 13:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 13:08 [PATCH v1 00/14] mpt3sas: Add support for multi-port path topology Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 01/14] mpt3sas: Define hba_port structure Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 02/14] mpt3sas: Allocate memory for hba_port objects Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 03/14] mpt3sas: Rearrange _scsih_mark_responding_sas_device() Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 04/14] mpt3sas: Update hba_port's sas_address & phy_mask Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 05/14] mpt3sas: Get device objects using sas_address & portID Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 06/14] mpt3sas: Rename transport_del_phy_from_an_existing_port Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 07/14] mpt3sas: Get sas_device objects using device's rphy Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 08/14] mpt3sas: Update hba_port objects after host reset Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 09/14] mpt3sas: Set valid PhysicalPort in SMPPassThrough Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 10/14] mpt3sas: Handling HBA vSES device Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 11/14] mpt3sas: Add bypass_dirty_port_flag parameter Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 12/14] mpt3sas: Handle vSES vphy object during HBA reset Sreekanth Reddy
2020-10-27 13:08 ` [PATCH v1 13/14] mpt3sas: add module parameter multipath_on_hba Sreekanth Reddy
2020-10-27 13:08 ` Sreekanth Reddy [this message]
2020-11-05 2:58 ` [PATCH v1 00/14] mpt3sas: Add support for multi-port path topology Martin K. Petersen
2020-11-11 2:58 ` 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=20201027130847.9962-15-sreekanth.reddy@broadcom.com \
--to=sreekanth.reddy@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sathya.prakash@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.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.