public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Felix Schnizlein <fschnizlein@suse.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	yanmin.zhang@intel.com, mingo@redhat.com, trenn@suse.com
Subject: Re: [PATCH v3 0/3] cpuinfo: implement cpuinfo in sysfs
Date: Mon, 28 Aug 2017 17:36:42 +0200	[thread overview]
Message-ID: <20170828153642.GA29792@kroah.com> (raw)
In-Reply-To: <20170828152906.GA2810@kroah.com>

On Mon, Aug 28, 2017 at 05:29:06PM +0200, Greg KH wrote:
> On Wed, Aug 09, 2017 at 07:37:23PM +0200, Felix Schnizlein wrote:
> > Make data from current /proc/cpuinfo available in sysfs.
> > 
> > Some parts of /proc/cpuinfo are already accessible through sysfs like
> > microcode, topology and cache info.
> > Now migrate the rest of worthful cpuinfo data.
> > 
> > While ACPI, cpufreq and most of /proc/cpuinfo data has already been migrated
> > to sysfs, this is another step in transitioning from proc to sysfs.
> > 
> > This patch series provides the architecture independent interface in
> > drivers/base/cpuinfo.c and the x86 and arm64 implementations 
> > in 3 separate patches.
> > 
> > More architectures can now be added easily by looking at the x86 patch.
> 
> Nice job, thanks for sticking with this, now applied.

Oops, no, it breaks the build:

make[2]: *** No rule to make target 'arch/x86/kernel/cpuinfo.o', needed by 'arch/x86/kernel/built-in.o'.  Stop.
make[1]: *** [scripts/Makefile.build:561: arch/x86/kernel] Error 2
make: *** [Makefile:1019: arch/x86] Error 2

You did test this, right?

Please fix and resend...

thanks,

greg k-h

      reply	other threads:[~2017-08-28 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1502300246-46144-1-git-send-email-fschnizlein@suse.com>
2017-08-28 15:29 ` [PATCH v3 0/3] cpuinfo: implement cpuinfo in sysfs Greg KH
2017-08-28 15:36   ` Greg KH [this message]

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=20170828153642.GA29792@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=fschnizlein@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=trenn@suse.com \
    --cc=x86@kernel.org \
    --cc=yanmin.zhang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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