From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Nilesh Javali <njavali@marvell.com>
Cc: Christoph Hellwig <hch@lst.de>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
GR-QLogic-Storage-Upstream
<GR-QLogic-Storage-Upstream@marvell.com>,
Bikash Hazarika <bhazarika@marvell.com>,
Anil Gurumurthy <agurumurthy@marvell.com>,
Shreyas Deodhar <sdeodhar@marvell.com>,
Shreya Jeurkar <sjeurkar@marvell.com>,
Jeetendra Sonar <jsonar@marvell.com>
Subject: Re: [EXT] Re: [PATCH v2] nvme-fc: initialize nvme fc ctrl ops
Date: Wed, 22 Feb 2023 12:04:14 -0500 [thread overview]
Message-ID: <yq1o7ploei6.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CO6PR18MB4500B97E46D7749B2D957836AFAA9@CO6PR18MB4500.namprd18.prod.outlook.com> (Nilesh Javali's message of "Wed, 22 Feb 2023 05:59:54 +0000")
Hi Nilesh!
> The 6.3/scsi-staging or 6.3/scsi-queue branches are still at
> 6.2.0-rc1. That could be the reason we hit the NVMe discovery NULL
> pointer dereference issue. Any plans to pull the below commit to
> 6.3/scsi-staging or 6.3/scsi-queue branches. Or am I missing
> something here.
Except in very rare circumstances, the SCSI submission trees stay at
-rc1 forever. I generally don't bring in stuff from other trees to avoid
problems if those trees subsequently have to rebase.
It sounds like you should be testing either linux-next or maybe a local
ephemeral integration branch featuring the various topic areas that are
important to you (SCSI fixes + staging, block, NVMe).
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-02-22 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 9:57 [PATCH v2] nvme-fc: initialize nvme fc ctrl ops Nilesh Javali
2023-02-21 17:35 ` Christoph Hellwig
2023-02-22 5:59 ` [EXT] " Nilesh Javali
2023-02-22 16:11 ` Niklas Cassel
2023-02-22 17:04 ` Martin K. Petersen [this message]
2023-02-23 15:43 ` Nilesh Javali
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=yq1o7ploei6.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=agurumurthy@marvell.com \
--cc=bhazarika@marvell.com \
--cc=hch@lst.de \
--cc=jsonar@marvell.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=njavali@marvell.com \
--cc=sdeodhar@marvell.com \
--cc=sjeurkar@marvell.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