Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210416124044.53d4beee@canb.auug.org.au> <BYAPR12MB323890BEC6212E401D10545EFB4C9@BYAPR12MB3238.namprd12.prod.outlook.com>
 <20210416140848.6f458345@canb.auug.org.au> <BYAPR12MB3238224BD17317FCC2975CFBFB4C9@BYAPR12MB3238.namprd12.prod.outlook.com>
In-Reply-To: <BYAPR12MB3238224BD17317FCC2975CFBFB4C9@BYAPR12MB3238.namprd12.prod.outlook.com>
From:   Alex Deucher <alexdeucher@gmail.com>
Date:   Fri, 16 Apr 2021 01:51:41 -0400
Message-ID: <CADnq5_Nr-NT9ku2J6gZ2YWgUQi+X-UAi-3QrEm5F2a30MRd11A@mail.gmail.com>
Subject: Re: linux-next: build warning after merge of the amdgpu tree
To:     "Liang, Prike" <Prike.Liang@amd.com>
Cc:     Stephen Rothwell <sfr@canb.auug.org.au>,
        "S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Apr 16, 2021 at 1:47 AM Liang, Prike <Prike.Liang@amd.com> wrote:
>
> [AMD Public Use]
>
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Sent: Friday, April 16, 2021 12:09 PM
> > To: Liang, Prike <Prike.Liang@amd.com>
> > Cc: Alex Deucher <alexdeucher@gmail.com>; S-k, Shyam-sundar <Shyam-
> > sundar.S-k@amd.com>; Linux Kernel Mailing List <linux-
> > kernel@vger.kernel.org>; Linux Next Mailing List <linux-next@vger.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@amd.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.

I'll drop it for now.  I just have it in there temporarily while it
makes its way upstream because a lot of people use this branch and it
fixes an important bug.

Alex