From: Thomas Gleixner <tglx@linutronix•de>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
X86 ML <x86@kernel•org>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Felix Schnizlein <fschnizlein@suse•com>,
Borislav Petkov <bp@alien8•de>
Subject: Re: linux-next: Tree for Sep 19 (x86/kernel/cpuinfo.c)
Date: Tue, 26 Sep 2017 09:40:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1709260930220.1941@nanos> (raw)
In-Reply-To: <46a06a76-a17c-de77-362a-99a18efaee79@infradead.org>
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
next prev parent reply other threads:[~2017-09-26 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 4:15 linux-next: Tree for Sep 19 Stephen Rothwell
2017-09-19 15:49 ` linux-next: Tree for Sep 19 (drivers/gpu/drm/i915/i915_gem.c) Randy Dunlap
2017-09-19 15:54 ` linux-next: Tree for Sep 19 (x86/kernel/cpuinfo.c) Randy Dunlap
2017-09-26 1:19 ` Randy Dunlap
2017-09-26 7:40 ` Thomas Gleixner [this message]
2017-09-26 8:18 ` Greg Kroah-Hartman
2017-09-26 10:40 ` Thomas Gleixner
2017-09-26 12:36 ` Felix Schnizlein
2017-09-26 16:00 ` Thomas Gleixner
2017-09-26 21:18 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1709260930220.1941@nanos \
--to=tglx@linutronix$(echo .)de \
--cc=bp@alien8$(echo .)de \
--cc=fschnizlein@suse$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox