[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1709260930220.1941@nanos>
Date: Tue, 26 Sep 2017 09:40:00 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Randy Dunlap <rdunlap@...radead.org>
cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
X86 ML <x86@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Felix Schnizlein <fschnizlein@...e.com>,
Borislav Petkov <bp@...en8.de>
Subject: Re: linux-next: Tree for Sep 19 (x86/kernel/cpuinfo.c)
On Mon, 25 Sep 2017, Randy Dunlap wrote:
> On 09/19/17 08:54, Randy Dunlap wrote:
> > On 09/18/17 21:15, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Changes since 20170918:
> >>
> >> Linus' tree still had its build failure for which I reverted a commit.
> >>
> >
> > on i386:
> >
> > ../arch/x86/kernel/cpuinfo.c: In function 'cpuinfo_flags':
Where does this file come from? Random driver code added to arch/x86? This
was neither acked nor reviewed by any x86 maintainer and just slapped into
arch/x86/kernel/ without spending a split second of brain to find the spot
where it actually belongs. It's not rocket science to figure that out.
Please revert.
Thanks,
tglx
Powered by blists - more mailing lists