From: Salvatore Bonaccorso <carnil@debian.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org,
Ranjan Kumar <ranjan.kumar@broadcom.com>,
rajsekhar.chundru@broadcom.com, sathya.prakash@broadcom.com,
sumit.saxena@broadcom.com
Subject: Re: [PATCH 0/6] This patchset contains critical Bug fixes
Date: Mon, 27 Mar 2023 18:13:21 +0200 [thread overview]
Message-ID: <ZCHAoUJaJLRRB9wf@eldamar.lan> (raw)
In-Reply-To: <167815780205.2075334.9513188954583912224.b4-ty@oracle.com>
Hi,
On Mon, Mar 06, 2023 at 09:57:26PM -0500, Martin K. Petersen wrote:
> On Tue, 28 Feb 2023 06:08:29 -0800, Ranjan Kumar wrote:
>
> > This patchset contains critical Bug fixes
> >
> > Ranjan Kumar (6):
> > mpi3mr: IOCTL timeout when disable/enable Interpt
> > mpi3mr: Driver unload crash host when enhanced logging is enabled
> > mpi3mr: Wait for diagnostic save during controller init
> > mpi3mr: appropriate return values for failures in firmware init path
> > mpi3mr: NVMe commands size greater than 8K fails
> > mpi3mr: Bad drive in topology results kernel crash
> >
> > [...]
>
> Applied to 6.3/scsi-fixes, thanks!
Will those be backported as well as needed to at least 6.1.y where
impacted? It was noticed that the patches do not contain Fixes tags
and no CC to stable@ so they might not be picked automatically for
stable series.
Regards,
Salvatore
next prev parent reply other threads:[~2023-03-27 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 14:08 [PATCH 0/6] This patchset contains critical Bug fixes Ranjan Kumar
2023-02-28 14:08 ` [PATCH 1/6] mpi3mr: IOCTL timeout when disable/enable Interpt Ranjan Kumar
2023-02-28 14:08 ` [PATCH 2/6] mpi3mr: Driver unload crash host when enhanced logging is enabled Ranjan Kumar
2023-02-28 14:08 ` [PATCH 3/6] mpi3mr: Wait for diagnostic save during controller init Ranjan Kumar
2023-02-28 14:08 ` [PATCH 4/6] mpi3mr: appropriate return values for failures in firmware init path Ranjan Kumar
2023-02-28 14:08 ` [PATCH 5/6] mpi3mr: NVMe commands size greater than 8K fails Ranjan Kumar
2023-02-28 14:08 ` [PATCH 6/6] mpi3mr: Bad drive in topology results kernel crash Ranjan Kumar
2023-03-07 2:57 ` [PATCH 0/6] This patchset contains critical Bug fixes Martin K. Petersen
2023-03-27 16:13 ` Salvatore Bonaccorso [this message]
2023-04-03 1:04 ` 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=ZCHAoUJaJLRRB9wf@eldamar.lan \
--to=carnil@debian.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rajsekhar.chundru@broadcom.com \
--cc=ranjan.kumar@broadcom.com \
--cc=sathya.prakash@broadcom.com \
--cc=sumit.saxena@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox