From: Christoph Hellwig <hch@lst.de>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Ming Lei <ming.lei@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>, lkp <lkp@intel.com>,
"kbuild-all@01.org" <kbuild-all@01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Omar Sandoval <osandov@fb.com>,
Christoph Hellwig <hch@lst.de>,
"Wu, Fengguang" <fengguang.wu@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Subject: Re: ERROR: "paddr_to_nid" [drivers/md/raid1.ko] undefined!
Date: Sat, 04 May 2019 06:27:34 +0000 [thread overview]
Message-ID: <20190504062734.GA30427@lst.de> (raw)
In-Reply-To: <0f33a863-4371-06cb-f4bd-1f95165b18f1@physik.fu-berlin.de>
On Sat, May 04, 2019 at 07:47:08AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Tony!
>
> On 5/3/19 10:25 PM, Luck, Tony wrote:
> > Big difference is I'm doing a natinve build with a much older compiler (4.6.4)
>
> Just as a heads-up: There are updated installation images available
> for Debian unstable for ia64 [1]. Those install a fresh system using GRUB
> as a bootloader and come with the latest versions of the toolchain.
Do we also have an x86 to ia64 cross compiler package for Debian?
Those packages really help me with changes to other architectures, and
the lack of them for ia64 makes compile-testing ia64 code rather painful.
next prev parent reply other threads:[~2019-05-04 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201905032019.tzlqufi0%lkp@intel.com>
2019-05-03 20:02 ` ERROR: "paddr_to_nid" [drivers/md/raid1.ko] undefined! Randy Dunlap
2019-05-03 20:10 ` Luck, Tony
2019-05-03 20:25 ` Luck, Tony
2019-05-03 20:54 ` Randy Dunlap
2019-05-04 5:47 ` John Paul Adrian Glaubitz
2019-05-04 6:27 ` Christoph Hellwig [this message]
2019-05-04 6:33 ` John Paul Adrian Glaubitz
2019-05-04 6:37 ` Christoph Hellwig
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=20190504062734.GA30427@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=fenghua.yu@intel.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kbuild-all@01.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=rdunlap@infradead.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