From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: page_types.h unification of declarations
Date: Tue, 14 Apr 2009 12:20:49 +0300 [thread overview]
Message-ID: <1239700849.24789.5.camel@penberg-laptop> (raw)
In-Reply-To: <1239693869.3033.31.camel@ht.satnam>
On Tue, 2009-04-14 at 12:54 +0530, Jaswinder Singh Rajput wrote:
> Impact: unification of declarations, cleanup
>
> Unification of declarations:
> moved init_memory_mapping, initmem_init and free_initmem from
> page_XX_types.h to page_types.h
>
> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
Looks good to me!
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
next prev parent reply other threads:[~2009-04-14 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 7:24 [PATCH -tip] x86: page_types.h unification of declarations Jaswinder Singh Rajput
2009-04-14 9:20 ` Pekka Enberg [this message]
2009-04-14 10:01 ` [tip:x86/mm] " tip-bot for Jaswinder Singh Rajput
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=1239700849.24789.5.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@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