linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Meneghini <jmeneghi@redhat.com>
To: Karan Tilak Kumar <kartilak@cisco.com>, sebaddel@cisco.com
Cc: arulponn@cisco.com, djhawar@cisco.com, gcboffa@cisco.com,
	mkai2@cisco.com, satishkh@cisco.com, aeasi@cisco.com,
	jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	revers@redhat.com, dan.carpenter@linaro.org
Subject: Re: [PATCH v4 5/5] scsi: fnic: Increment driver version number
Date: Fri, 13 Jun 2025 17:10:36 -0400	[thread overview]
Message-ID: <0b930c3e-0835-429e-8081-d83df811a091@redhat.com> (raw)
In-Reply-To: <20250612221805.4066-5-kartilak@cisco.com>

Since we are making a major fix to the driver here do we want to squash this change
together with

[PATCH v4 2/5] scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out

so that the driver version gets updated in Stable together with the bug fix?

/John

On 6/12/25 6:18 PM, Karan Tilak Kumar wrote:
> Increment driver version number.
> 
> Reviewed-by: Sesidhar Baddela <sebaddel@cisco.com>
> Reviewed-by: Arulprabhu Ponnusamy <arulponn@cisco.com>
> Reviewed-by: Gian Carlo Boffa <gcboffa@cisco.com>
> Reviewed-by: Arun Easi <aeasi@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 6c5f6046b1f5..86e293ce530d 100644
> --- a/drivers/scsi/fnic/fnic.h
> +++ b/drivers/scsi/fnic/fnic.h
> @@ -30,7 +30,7 @@
>   
>   #define DRV_NAME		"fnic"
>   #define DRV_DESCRIPTION		"Cisco FCoE HBA Driver"
> -#define DRV_VERSION		"1.8.0.0"
> +#define DRV_VERSION		"1.8.0.1"
>   #define PFX			DRV_NAME ": "
>   #define DFX                     DRV_NAME "%d: "
>   


  reply	other threads:[~2025-06-13 21:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 22:18 [PATCH v4 1/5] scsi: fnic: Set appropriate logging level for log message Karan Tilak Kumar
2025-06-12 22:18 ` [PATCH v4 2/5] scsi: fnic: Fix crash in fnic_wq_cmpl_handler when FDMI times out Karan Tilak Kumar
2025-06-12 22:18 ` [PATCH v4 3/5] scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths Karan Tilak Kumar
2025-06-13 21:05   ` John Meneghini
2025-06-13 21:46     ` Karan Tilak Kumar (kartilak)
2025-06-12 22:18 ` [PATCH v4 4/5] scsi: fnic: Turn off FDMI ACTIVE flags on link down Karan Tilak Kumar
2025-06-13 20:28   ` John Meneghini
2025-06-13 21:59     ` Karan Tilak Kumar (kartilak)
2025-06-16 14:35       ` John Meneghini
2025-06-16 16:31         ` Karan Tilak Kumar (kartilak)
2025-06-12 22:18 ` [PATCH v4 5/5] scsi: fnic: Increment driver version number Karan Tilak Kumar
2025-06-13 21:10   ` John Meneghini [this message]
2025-06-13 20:34 ` [PATCH v4 1/5] scsi: fnic: Set appropriate logging level for log message John Meneghini
2025-06-13 21:45   ` 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=0b930c3e-0835-429e-8081-d83df811a091@redhat.com \
    --to=jmeneghi@redhat.com \
    --cc=aeasi@cisco.com \
    --cc=arulponn@cisco.com \
    --cc=dan.carpenter@linaro.org \
    --cc=djhawar@cisco.com \
    --cc=gcboffa@cisco.com \
    --cc=jejb@linux.ibm.com \
    --cc=kartilak@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mkai2@cisco.com \
    --cc=revers@redhat.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;
as well as URLs for NNTP newsgroup(s).