public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@queued.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Young <hidave.darkstar@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-06-11-16-40 uploaded
Date: Sat, 12 Jun 2010 01:59:37 -0400	[thread overview]
Message-ID: <20100612015937.1981f1b6@dev.queued.net> (raw)
In-Reply-To: <20100611195421.6b723910.akpm@linux-foundation.org>

On Fri, 11 Jun 2010 19:54:21 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Sat, 12 Jun 2010 10:43:31 +0800 Dave Young
> <hidave.darkstar@gmail.com> wrote:
> 
> > On Sat, Jun 12, 2010 at 7:40 AM,  <akpm@linux-foundation.org> wrote:
> > > The mm-of-the-moment snapshot 2010-06-11-16-40 has been uploaded
> > > to
> > >
> > > __ http://userweb.kernel.org/~akpm/mmotm/
> > >
> > > and will soon be available at
> > >
> > > __ git://zen-kernel.org/kernel/mmotm.git
> > >
> > 
> > Hi, andrew
> > 
> > building failed with:
> >   AS      arch/x86/kernel/entry_32.o
> > /home/dave/src/linux-2.6.35/arch/x86/include/asm/olpc_ofw.h:
> > Assembler
> > messages: /home/dave/src/linux-2.6.35/arch/x86/include/asm/olpc_ofw.h:29:
> > Error: no such instruction: `static inline void
> > olpc_ofw_detect_range(void){}' make[2]: ***
> > [arch/x86/kernel/entry_32.o] Error 1 make[1]: *** [arch/x86/kernel]
> > Error 2 make: *** [arch/x86] Error 2
> > 
> > Attached a patch to fix it (I have not appropriate email client now,
> > sorry for the inconvenience )
> 
> Thanks.
> 
> We can simplify things a bit I think...
> 
> #ifndef _ASM_X86_OLPC_OFW_H
> #define _ASM_X86_OLPC_OFW_H
> 
> /* hardcode addresses to make life easier dealing w/ VMALLOC_END and
> others */ #define OLPC_OFW_START 0xff800000UL
> #define OLPC_OFW_SIZE (PGDIR_SIZE)
> #define OLPC_OFW_END (OLPC_OFW_START + OLPC_OFW_SIZE)
> 
> #ifndef __ASSEMBLER__
> 
> #ifdef CONFIG_OLPC_OPENFIRMWARE
> 
> /* address of OFW callback interface; will be NULL if OFW isn't found
> */ extern int (*olpc_ofw_cif)(int *);
> 
> /* page dir entry containing OFW's current memory */
> extern pgdval_t olpc_ofw_pgd;
> 
> /* run an OFW command by calling into the firmware */
> extern int olpc_ofw(const char *name, int nr_args, int nr_res, ...);
> 
> /* determine/ensure OFW lives in the proper place in (virtual) memory
> */ void olpc_ofw_detect_range(void);
> 
> #else	/* CONFIG_OLPC_OPENFIRMWARE */
> 
> static inline void olpc_ofw_detect_range(void) { }
> 
> #endif	/* CONFIG_OLPC_OPENFIRMWARE */
> 
> #endif	/* __ASSEMBLER__ */
> 
> #endif
>

Thanks, I've changed it to something similar in my git tree.  It'll be
in the next patch (once I've addressed hpa's concerns).

  reply	other threads:[~2010-06-12  5:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 23:40 mmotm 2010-06-11-16-40 uploaded akpm
2010-06-12  0:22 ` Andrew Morton
2010-06-12  1:31 ` Randy Dunlap
2010-06-12  1:48   ` Andrew Morton
2010-06-12  2:43 ` Dave Young
2010-06-12  2:54   ` Andrew Morton
2010-06-12  5:59     ` Andres Salomon [this message]
2010-06-12  8:50 ` mmotm 2010-06-11-16-40 uploaded - busticated patch? Valdis.Kletnieks
2010-06-12 15:37 ` mmotm 2010-06-11-16-40 uploaded Stephen Rothwell
2010-06-12 17:10   ` Andrew Morton
2010-06-13  3:38     ` Stephen Rothwell

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=20100612015937.1981f1b6@dev.queued.net \
    --to=dilinger@queued.net \
    --cc=akpm@linux-foundation.org \
    --cc=hidave.darkstar@gmail.com \
    --cc=linux-kernel@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