From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-arch@vger.kernel.org
Subject: Re: let __dec_zone_page_state use __dec_zone_state
Date: Fri, 29 Feb 2008 08:45:27 +0100 [thread overview]
Message-ID: <20080229074527.GA32230@digi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802271108500.32462@schroedinger.engr.sgi.com>
Hello Christoph,
Christoph Lameter wrote:
> On Mon, 25 Feb 2008, Uwe Kleine-König wrote:
>
> > This removes code duplication and makes __dec_zone_page_state look like
> > __inc_zone_page_state.
>
> Acked-by: Christoph Lameter <clameter@sgi.com>
Unless Linus or Andrew take that patch I think the best path for that
patch into mainline is going over your tree.
Best regards
Uwe
--
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962
next prev parent reply other threads:[~2008-02-29 7:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 13:26 regression: 2f569af (CONFIG_HIGHPTE vs. sub-page page tables.) Uwe Kleine-König
2008-02-25 13:38 ` Russell King
2008-02-25 15:32 ` Uwe Kleine-König
2008-02-25 15:45 ` let __dec_zone_page_state use __dec_zone_state Uwe Kleine-König
2008-02-27 19:10 ` Christoph Lameter
2008-02-29 7:45 ` Uwe Kleine-König [this message]
2008-02-29 19:32 ` Christoph Lameter
2008-02-25 16:56 ` regression: 2f569af (CONFIG_HIGHPTE vs. sub-page page tables.) Martin Schwidefsky
2008-02-26 14:38 ` Uwe Kleine-König
2008-02-26 17:57 ` Martin Schwidefsky
2008-02-26 19:49 ` Russell King
2008-02-27 12:44 ` Uwe Kleine-König
2008-02-27 14:21 ` Martin Schwidefsky
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=20080229074527.GA32230@digi.com \
--to=uwe.kleine-koenig@digi.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.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).