linux-kernel - Re: linux-next: build warning after merge of the amdgpu tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADnq5_Nr-NT9ku2J6gZ2YWgUQi+X-UAi-3QrEm5F2a30MRd11A@mail.gmail.com>
Date:   Fri, 16 Apr 2021 01:51:41 -0400
From:   Alex Deucher <alexdeucher@...il.com>
To:     "Liang, Prike" <Prike.Liang@....com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        "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

On Fri, Apr 16, 2021 at 1:47 AM Liang, Prike <Prike.Liang@....com> wrote:
>
> [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.

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