[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR12MB3238224BD17317FCC2975CFBFB4C9@BYAPR12MB3238.namprd12.prod.outlook.com>
Date: Fri, 16 Apr 2021 05:47:03 +0000
From: "Liang, Prike" <Prike.Liang@....com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Alex Deucher <alexdeucher@...il.com>,
"S-k, Shyam-sundar" <Shyam-sundar.S-k@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: RE: linux-next: build warning after merge of the amdgpu tree
[AMD Public Use]
> From: Stephen Rothwell <sfr@...b.auug.org.au>
> Sent: Friday, April 16, 2021 12:09 PM
> To: Liang, Prike <Prike.Liang@....com>
> Cc: Alex Deucher <alexdeucher@...il.com>; S-k, Shyam-sundar <Shyam-
> sundar.S-k@....com>; Linux Kernel Mailing List <linux-
> kernel@...r.kernel.org>; Linux Next Mailing List <linux-next@...r.kernel.org>
> Subject: Re: linux-next: build warning after merge of the amdgpu tree
>
> Hi,
>
> On Fri, 16 Apr 2021 03:12:12 +0000 "Liang, Prike" <Prike.Liang@....com>
> wrote:
> >
> > Hi, Rothwell
>
> (Stephen, actually :-))
>
> > This fix solution hasn't locked down and still being discussed and roll-
> updated in the NVMe mail group.
> > Will update the patch once it refined done.
>
> In which case, this patch should not be in linux-next (or any branch that is
> included by linux-next).
>
How about revert the patch temporally ? Once lock down the solution and will land in the final latest patch.
> --
> Cheers,
> Stephen Rothwell
Powered by blists - more mailing lists