From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Recent SPARSEMEM and DISCONTIG changes break some builds
Date: Tue, 01 Nov 2005 00:25:28 +0000 [thread overview]
Message-ID: <20051101002528.GJ6019@localhost.localdomain> (raw)
In-Reply-To: <17253.37207.664571.236714@wombat.chubb.wattle.id.au>
luck wrote: [Mon Oct 31 2005, 02:00:46PM EST]
> >Your build must be against -mm because pfn_to_kaddr shouldn't be required
> >in 2.6.14. The patch below will fix this.
>
> I was building 2.6.14+(all the bits in Linus' git tree that I pulled
> at about 8:30 PST today). Presumably this bit has already been moved
> from -mm to -linus?
Actually you are correct. I just updated my local Linus' git tree and
pfn_to_kaddr is now required for ia64 because of changes in mm/sparse.c.
>
> Thanks for the patch, I'll give it a spin.
your welcome.
>
> -Tony
> -
bob
next prev parent reply other threads:[~2005-11-01 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 3:36 Recent SPARSEMEM and DISCONTIG changes break some builds Peter Chubb
2005-10-31 17:45 ` Luck, Tony
2005-10-31 18:25 ` Bob Picco
2005-10-31 19:00 ` Luck, Tony
2005-11-01 0:25 ` Bob Picco [this message]
2005-11-01 0:31 ` Peter Chubb
2005-11-01 0:46 ` Luck, Tony
2005-11-01 2:11 ` Peter Chubb
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=20051101002528.GJ6019@localhost.localdomain \
--to=bob.picco@hp.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox