From: Nathan Chancellor <natechancellor@gmail.com>
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>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: linux-next: Tree for Sep 29 (drivers/acpi/nfit/core.c)
Date: Tue, 29 Sep 2020 12:51:41 -0700 [thread overview]
Message-ID: <20200929195141.GA917771@ubuntu-m3-large-x86> (raw)
In-Reply-To: <8b5a54fc-39bc-ae2b-9710-f2493400cdf6@infradead.org>
On Tue, Sep 29, 2020 at 12:47:42PM -0700, Randy Dunlap wrote:
> On 9/29/20 2:29 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200928:
> >
>
> on x86_64:
> when CONFIG_ACPI_NUMA is not set/enabled:
>
> ../drivers/acpi/nfit/core.c: In function ‘acpi_nfit_register_region’:
> CC lib/ts_bm.o
> ../drivers/acpi/nfit/core.c:3010:27: error: implicit declaration of function ‘pxm_to_node’; did you mean ‘xa_to_node’? [-Werror=implicit-function-declaration]
> ndr_desc->target_node = pxm_to_node(spa->proximity_domain);
> ^~~~~~~~~~~
> xa_to_node
>
> Full randconfig file is attached.
>
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
I independently found this and sent a patch:
https://lore.kernel.org/lkml/20200928194554.3423466-1-natechancellor@gmail.com/
Feel free to reply with a tag if it works for you as well.
Cheers,
Nathan
prev parent reply other threads:[~2020-09-29 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 9:29 linux-next: Tree for Sep 29 Stephen Rothwell
2020-09-29 19:47 ` linux-next: Tree for Sep 29 (drivers/acpi/nfit/core.c) Randy Dunlap
2020-09-29 19:51 ` Nathan Chancellor [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=20200929195141.GA917771@ubuntu-m3-large-x86 \
--to=natechancellor@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®