From: James Smart <jsmart2021@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: James Smart <jsmart2021@gmail.com>,
Dick Kennedy <dick.kennedy@broadcom.com>,
James Smart <james.smart@broadcom.com>
Subject: [PATCH v2 12/13] lpfc: update driver version to 12.0.0.0
Date: Tue, 6 Feb 2018 18:28:50 -0800 [thread overview]
Message-ID: <20180207022851.11800-13-jsmart2021@gmail.com> (raw)
In-Reply-To: <20180207022851.11800-1-jsmart2021@gmail.com>
Update the driver version to 12.0.0.0
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <james.smart@broadcom.com>
---
drivers/scsi/lpfc/lpfc_version.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/lpfc/lpfc_version.h b/drivers/scsi/lpfc/lpfc_version.h
index 4adbf07880a2..b1ae62a44aae 100644
--- a/drivers/scsi/lpfc/lpfc_version.h
+++ b/drivers/scsi/lpfc/lpfc_version.h
@@ -20,7 +20,7 @@
* included with this package. *
*******************************************************************/
-#define LPFC_DRIVER_VERSION "11.4.0.7"
+#define LPFC_DRIVER_VERSION "12.0.0.0"
#define LPFC_DRIVER_NAME "lpfc"
/* Used for SLI 2/3 */
--
2.13.1
next prev parent reply other threads:[~2018-02-07 2:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 2:28 [PATCH v2 00/13] lpfc new hardware patches for 12.0.0.0 James Smart
2018-02-07 2:28 ` [PATCH v2 01/13] lpfc: Rework lpfc to allow different sli4 cq and eq handlers James Smart
2018-02-07 9:01 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 02/13] lpfc: Rework sli4 doorbell infrastructure James Smart
2018-02-07 9:13 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 03/13] lpfc: Add SLI-4 if_type=6 support to the code base James Smart
2018-02-07 9:17 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 04/13] lpfc: Add push-to-adapter support to sli4 James Smart
2018-02-07 9:51 ` Johannes Thumshirn
2018-02-07 10:27 ` Johannes Thumshirn
2018-02-07 15:42 ` James Smart
2018-02-13 5:59 ` Michael Ellerman
2018-02-13 17:37 ` James Smart
2018-02-07 2:28 ` [PATCH v2 05/13] lpfc: Add PCI Ids for if_type=6 hardware James Smart
2018-02-07 9:52 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 06/13] lpfc: Add 64G link speed support James Smart
2018-02-07 9:58 ` Johannes Thumshirn
2018-02-07 15:38 ` James Smart
2018-02-07 15:40 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 07/13] lpfc: Add if_type=6 support for cycling valid bits James Smart
2018-02-07 10:01 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 08/13] lpfc: Enable fw download on if_type=6 devices James Smart
2018-02-07 10:03 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 09/13] lpfc: Add embedded data pointers for enhanced performance James Smart
2018-02-07 10:17 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 10/13] lpfc: Fix nvme embedded io length on new hardware James Smart
2018-02-07 10:32 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 11/13] lpfc: Work around NVME cmd iu SGL type James Smart
2018-02-07 10:39 ` Johannes Thumshirn
2018-02-07 2:28 ` James Smart [this message]
2018-02-07 10:39 ` [PATCH v2 12/13] lpfc: update driver version to 12.0.0.0 Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 13/13] lpfc: Update 12.0.0.0 modified files for 2018 Copyright James Smart
2018-02-07 10:50 ` Johannes Thumshirn
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=20180207022851.11800-13-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
/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).