From: Christoph Lameter <clameter@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
apw@shadowen.org, Sam Ravnborg <sam@ravnborg.org>,
linux-mm@kvack.org
Subject: Re: [patch 02/19] x86: Use kbuild.h
Date: Wed, 16 Apr 2008 10:44:55 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804161044250.12019@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080416141023.GA25280@elte.hu>
On Wed, 16 Apr 2008, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > * Christoph Lameter <clameter@sgi.com> wrote:
> >
> > > Drop the macro definitions in asm-offsets_*.c and use kbuild.h
> >
> > thanks Christoph, applied.
>
> the dependency i missed was the existence of include/linux/kbuild.h ;-)
> Anyway:
>
> Acked-by: Ingo Molnar <mingo@elte.hu>
Yes sorry this is dependent on other patches merged by Andrew. This is the
classic case of arch changes that depend on core changes.
--
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>
next prev parent reply other threads:[~2008-04-16 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080414221846.967753424@sgi.com>
[not found] ` <20080414221808.269371488@sgi.com>
[not found] ` <20080414221846.735656759@sgi.com>
2008-04-14 22:22 ` [patch 10/19] blackfin: Use kbuild.h instead of defining macros in asm-macros.c Mike Frysinger
[not found] ` <20080414221848.428938934@sgi.com>
2008-04-15 8:14 ` [patch 17/19] Use kbuild.h instead of defining macros in asm-offsets.c Martin Schwidefsky
2008-04-15 9:55 ` [patch 11/19] frv: " David Howells
2008-04-15 19:09 ` Christoph Lameter
[not found] ` <20080414221844.876647987@sgi.com>
2008-04-16 13:01 ` [patch 02/19] x86: Use kbuild.h Ingo Molnar
2008-04-16 14:10 ` Ingo Molnar
2008-04-16 17:44 ` Christoph Lameter [this message]
2008-04-16 19:15 ` Andrew Morton
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=Pine.LNX.4.64.0804161044250.12019@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--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).