From: Krzysztof Kozlowski <krzk@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 3527/3539] ERROR: modpost: "max_low_pfn" undefined!
Date: Wed, 26 Aug 2020 22:32:57 +0200 [thread overview]
Message-ID: <CAJKOXPeW2psS_QFnjRacwdLaE8WNmtx35jQy2PkZyc_7SKDT6g@mail.gmail.com> (raw)
In-Reply-To: <202008270343.X5RfLhop%lkp@intel.com>
On Wed, 26 Aug 2020 at 21:06, kernel test robot <lkp@intel.com> wrote:
>
> Hi Krzysztof,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: f37be72473a007d5d66c52f6cdf43fc8c0961f95
> commit: 19bd695b0f7b5fc13f44645d0d0f446a6d7b7f99 [3527/3539] ia64: fix build error with !COREDUMP
My commit only pushed compilation further. Mentioned build errors seem
unrelated and most probably they were there already.
Best regards,
Krzysztpf
Looks like my fixup uncovered another build error
> config: ia64-randconfig-r012-20200826 (attached as .config)
> compiler: ia64-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 19bd695b0f7b5fc13f44645d0d0f446a6d7b7f99
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=ia64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> ERROR: modpost: "min_low_pfn" [drivers/mmc/core/mmc_core.ko] undefined!
> ERROR: modpost: "max_low_pfn" [drivers/mmc/core/mmc_core.ko] undefined!
prev parent reply other threads:[~2020-08-26 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 19:05 kernel test robot
2020-08-26 20:32 ` Krzysztof Kozlowski [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=CAJKOXPeW2psS_QFnjRacwdLaE8WNmtx35jQy2PkZyc_7SKDT6g@mail.gmail.com \
--to=krzk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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