From: Sachin Sant <sachinp@linux.ibm.com>
To: linux-cxl@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org
Subject: [linux-next] Build failure drivers/cxl/cxl_pmem (powerpc)
Date: Fri, 29 Jul 2022 09:31:42 +0530 [thread overview]
Message-ID: <7FF6D18F-2F85-4FFC-96B8-D1B1E8D8D622@linux.ibm.com> (raw)
Linux-next (5.19.0-rc8-next-20220728) fails to build on powerpc with
following error:
ERROR: modpost: "memory_add_physaddr_to_nid" [drivers/cxl/cxl_pmem.ko] undefined!
make[1]: *** [scripts/Makefile.modpost:128: modules-only.symvers] Error 1
The code in question was last changed by following patch:
commit 04ad63f086d1
cxl/region: Introduce cxl_pmem_region objects
- Sachin
WARNING: multiple messages have this Message-ID (diff)
From: Sachin Sant <sachinp@linux.ibm.com>
To: linux-cxl@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>
Cc: linux-next@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: [linux-next] Build failure drivers/cxl/cxl_pmem (powerpc)
Date: Fri, 29 Jul 2022 09:31:42 +0530 [thread overview]
Message-ID: <7FF6D18F-2F85-4FFC-96B8-D1B1E8D8D622@linux.ibm.com> (raw)
Linux-next (5.19.0-rc8-next-20220728) fails to build on powerpc with
following error:
ERROR: modpost: "memory_add_physaddr_to_nid" [drivers/cxl/cxl_pmem.ko] undefined!
make[1]: *** [scripts/Makefile.modpost:128: modules-only.symvers] Error 1
The code in question was last changed by following patch:
commit 04ad63f086d1
cxl/region: Introduce cxl_pmem_region objects
- Sachin
next reply other threads:[~2022-07-29 4:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 4:01 Sachin Sant [this message]
2022-07-29 4:01 ` [linux-next] Build failure drivers/cxl/cxl_pmem (powerpc) Sachin Sant
2022-07-29 6:17 ` Michael Ellerman
2022-07-29 6:17 ` Michael Ellerman
2022-07-29 7:18 ` Sachin Sant
2022-07-29 7:18 ` Sachin Sant
2022-07-29 14:35 ` Dan Williams
2022-07-29 14:35 ` Dan Williams
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=7FF6D18F-2F85-4FFC-96B8-D1B1E8D8D622@linux.ibm.com \
--to=sachinp@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.