linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: ak@suse.de, Sam Ravnborg <sam@ravnborg.org>,
	Mel Gorman <mel@csn.ul.ie>,
	apw@shadowen.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Rik van Riel <riel@redhat.com>,
	linux-mm@kvack.org
Subject: Re: [patch 2/8] Kbuild: Create a way to create preprocessor constants from C expressions
Date: Wed, 5 Mar 2008 20:08:00 -0800	[thread overview]
Message-ID: <20080305200800.23ee10ec.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080305223845.436523065@sgi.com>

On Wed, 05 Mar 2008 14:38:17 -0800 Christoph Lameter <clameter@sgi.com> wrote:

> The use of enums create constants that are not available to the preprocessor
> when building the kernel (f.e. MAX_NR_ZONES).
> 
> Arch code already has a way to export constants calculated to the
> preprocessor through the asm-offsets.c file. Generate something
> similar for the core kernel through kbuild.
> 

err, this patch needs help.

> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ linux-2.6/include/linux/bounds.h	2008-02-29 19:29:50.000000000 -0800
> @@ -0,0 +1,10 @@
> +#ifndef __LINUX_BOUNDS_H__
> +#define __LINUX_BOUNDS_H__
> +/*
> + * DO NOT MODIFY.
> + *
> + * This file was generated by Kbuild
> + *
> + */
> +
> +#endif

a) I'm not sure that we should check in a file which is supposed to get
   overwritten at build-time.

b) Is this `make O=' friendly?

c)
	make mrproper
	make allmodconfig
	make

In file included from include/linux/mm.h:192,
                 from include/linux/suspend.h:11,
                 from arch/x86/kernel/asm-offsets_64.c:12,
                 from arch/x86/kernel/asm-offsets.c:4:
include/linux/page-flags.h:10:26: error: linux/bounds.h: No such file or directory

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-03-06  4:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080305223815.574326323@sgi.com>
     [not found] ` <20080305223846.780991734@sgi.com>
2008-03-06  2:40   ` [patch 8/8] Pageflags: Eliminate PG_xxx aliases Nick Piggin
2008-03-06 22:51     ` Christoph Lameter
2008-03-07  0:48       ` Nick Piggin
2008-03-07  1:38         ` Christoph Lameter
2008-03-07  2:20           ` Nick Piggin
2008-03-07  3:53             ` Christoph Lameter
2008-03-07  4:16               ` Nick Piggin
     [not found] ` <20080305223845.436523065@sgi.com>
2008-03-06  4:08   ` Andrew Morton [this message]
2008-03-06 20:20     ` [patch 2/8] Kbuild: Create a way to create preprocessor constants from C expressions Christoph Lameter
2008-03-06 21:00       ` Sam Ravnborg
2008-03-06 21:49         ` Christoph Lameter
2008-03-06 22:43         ` Christoph Lameter
2008-03-06 22:55           ` Sam Ravnborg
2008-03-06 23:02             ` Christoph Lameter
2008-03-06 20:51   ` Sam Ravnborg

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=20080305200800.23ee10ec.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ak@suse.de \
    --cc=apw@shadowen.org \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=riel@redhat.com \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).