linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: kbuild test robot <fengguang.wu@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	Tony Luck <tony.luck@intel.com>
Subject: Re: [linux-next:master] BUILD REGRESSION a5444cde9dc2120612e50fc5a56c975e67a041fb
Date: Mon, 19 Mar 2018 18:10:13 -0700	[thread overview]
Message-ID: <d22bd482-2f5b-8c02-4821-9f1b02122b51@infradead.org> (raw)
In-Reply-To: <5ab048c0.wmRYTJi5ip8zBzJ4%fengguang.wu@intel.com>

On 03/19/2018 04:33 PM, kbuild test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git  master
> branch HEAD: a5444cde9dc2120612e50fc5a56c975e67a041fb  Add linux-next specific files for 20180319
> 
> Regressions in current branch:
> 
> ERROR: "__sw_hweight8" [drivers/net/wireless/mediatek/mt76/mt76.ko] undefined!

Well, the driver could do:

drivers/net/wireless/mediatek/mt76/Kconfig:

+	select GENERIC_HWEIGHT

but maybe arch/ix64/Kconfig (where the build error is) could be asked to do:

config GENERIC_HWEIGHT
	def_bool y

like 23 other $arch-es do.  Aha, ia64 provides inline functions via some
a twisty maze of header files.

Tony, Fengguang, what header(s) should be used to reach __arch_hweight8()?

thanks,
-- 
~Randy

  reply	other threads:[~2018-03-20  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 23:33 [linux-next:master] BUILD REGRESSION a5444cde9dc2120612e50fc5a56c975e67a041fb kbuild test robot
2018-03-20  1:10 ` Randy Dunlap [this message]
2018-03-20 18:41   ` Luck, Tony

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=d22bd482-2f5b-8c02-4821-9f1b02122b51@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).