Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Adrian Bunk <bunk@kernel.org>
Cc: Christoph Lameter <clameter@sgi.com>,
	kyle@parisc-linux.org, matthew@wil.cx, grundler@parisc-linux.org,
	linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: parisc compile error
Date: Thu, 7 Feb 2008 18:20:15 -0500	[thread overview]
Message-ID: <20080207232015.GA11653@phobos.i.cabal.ca> (raw)
In-Reply-To: <20080207231232.GF7198@cs181133002.pp.htv.fi>

On Fri, Feb 08, 2008 at 01:12:32AM +0200, Adrian Bunk wrote:
> Commit 9e2779fa281cfda13ac060753d674bbcaa23367e broke parisc:
> 
> <--  snip  -->
> 
> ...
>   CC      arch/parisc/kernel/asm-offsets.s
> In file included from include/asm/pgtable.h:13,
>                  from arch/parisc/kernel/asm-offsets.c:36:
> include/linux/mm.h: In function 'is_vmalloc_addr':
> include/linux/mm.h:243: error: 'VMALLOC_START' undeclared (first use in this function)
> include/linux/mm.h:243: error: (Each undeclared identifier is reported only once
> include/linux/mm.h:243: error: for each function it appears in.)
> include/linux/mm.h:243: error: 'VMALLOC_END' undeclared (first use in this function)
> make[1]: *** [arch/parisc/kernel/asm-offsets.s] Error 1
> 

yes, it's in my batch of fixes.

thanks for the reminder.

cheers, kyle

  reply	other threads:[~2008-02-07 23:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 23:12 parisc compile error Adrian Bunk
2008-02-07 23:20 ` Kyle McMartin [this message]
2008-02-07 23:33   ` Christoph Lameter
2008-02-07 23:34     ` Kyle McMartin
  -- strict thread matches above, loose matches on Subject: below --
2008-02-13  6:49 rubisher
2008-02-14  5:14 ` Kyle McMartin
2008-02-13 12:42 rubisher
2008-02-14  5:22 ` Kyle McMartin
2008-02-17 22:36 ` Kyle McMartin
2008-02-15 10:42 rubisher
2008-02-15 10:44 rubisher
2008-02-18 10:32 rubisher
2008-02-18 17:14 ` Kyle McMartin

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=20080207232015.GA11653@phobos.i.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=bunk@kernel.org \
    --cc=clameter@sgi.com \
    --cc=grundler@parisc-linux.org \
    --cc=kyle@parisc-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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