[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CO6PR18MB450028642111EB7570CDA0BCAF1DA@CO6PR18MB4500.namprd18.prod.outlook.com>
Date: Thu, 24 Aug 2023 14:10:00 +0000
From: Nilesh Javali <njavali@...vell.com>
To: "Martin K. Petersen" <martin.petersen@...cle.com>,
Stephen Rothwell <sfr@...b.auug.org.au>
CC: Manish Rangankar <mrangankar@...vell.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: RE: [EXT] Re: linux-next: build failure after merge of the scsi-mkp
tree
Hi Martin,
I have a fix for the CONFIG_NVME_FC enable check.
And I was planning to post other fixes for qla_iocb.c sparse warning and
usage of raw_smp_processor_id fix together.
In the interest of time, I will post these fixes individually.
Thanks,
Nilesh
> -----Original Message-----
> From: Martin K. Petersen <martin.petersen@...cle.com>
> Sent: Thursday, August 24, 2023 4:30 AM
> To: Stephen Rothwell <sfr@...b.auug.org.au>
> Cc: Martin K. Petersen <martin.petersen@...cle.com>; Manish Rangankar
> <mrangankar@...vell.com>; Nilesh Javali <njavali@...vell.com>; Linux
> Kernel Mailing List <linux-kernel@...r.kernel.org>; Linux Next Mailing List
> <linux-next@...r.kernel.org>
> Subject: [EXT] Re: linux-next: build failure after merge of the scsi-mkp tree
>
> External Email
>
> ----------------------------------------------------------------------
>
> Stephen,
>
> >> I have used the scsi-mkp tree from next-20230821 for today.
> >
> > Ping?
>
> Since it doesn't appear that a fix is imminent I'm going to drop this
> series.
>
> --
> Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists