public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: lkp <lkp@intel.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: drivers/base/topology.c:158:45: error: 'boot_cpu_data' undeclared; did you mean 'boot_cpu_init'?
Date: Thu, 21 Apr 2022 19:50:55 +0000	[thread overview]
Message-ID: <4401b87816cd40b9aea30b6eca5d21a4@intel.com> (raw)
In-Reply-To: <202204220317.dri1BV0q-lkp@intel.com>

> compiler: microblaze-linux-gcc (GCC) 11.2.0

Greg,

Ignore v2 patch. It seems that only arm64, ia64, mips, parisc, sh, um, and x86 have "boot_cpu_data".

LKP just found it breaks microblaze ... but it's going to break alpha, arc, arm. ... too :-(

Revert the ppin patch for now while I think harder on whether this can be done.

-Tony

      reply	other threads:[~2022-04-21 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 19:24 drivers/base/topology.c:158:45: error: 'boot_cpu_data' undeclared; did you mean 'boot_cpu_init'? kernel test robot
2022-04-21 19:50 ` Luck, Tony [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=4401b87816cd40b9aea30b6eca5d21a4@intel.com \
    --to=tony.luck@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@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