[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7E91BABF@ORSMSX104.amr.corp.intel.com>
Date: Fri, 3 May 2019 20:25:02 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Randy Dunlap <rdunlap@...radead.org>, lkp <lkp@...el.com>,
Ming Lei <ming.lei@...hat.com>
CC: "kbuild-all@...org" <kbuild-all@...org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jens Axboe <axboe@...nel.dk>, Omar Sandoval <osandov@...com>,
Christoph Hellwig <hch@....de>,
"Wu, Fengguang" <fengguang.wu@...el.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>
Subject: RE: ERROR: "paddr_to_nid" [drivers/md/raid1.ko] undefined!
>> Exporting paddr_to_nid() in arch/ia64/mm/numa.c fixes all of these build errors.
>> Is there a problem with doing that?
>
> I don't see a problem with exporting it.
But I also don't see these build errors. I'm using the same HEAD commit. I think the
same .config (derived from arch/ia64/configs/bigsur_defconfig.
Big difference is I'm doing a natinve build with a much older compiler (4.6.4)
-Tony
Powered by blists - more mailing lists