From: Andrew Morton <akpm@linux-foundation.org>
To: Jon Tollefson <kniht@linux.vnet.ibm.com>
Cc: nickpiggin@yahoo.com.au, kniht@linux.vnet.ibm.com,
dwg@au1.ibm.com, linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/1 v2] powerpc: hugetlb pgtable cache access cleanup
Date: Tue, 4 Nov 2008 13:32:31 -0800 [thread overview]
Message-ID: <20081104133231.fb224e68.akpm@linux-foundation.org> (raw)
In-Reply-To: <490A2F4D.7030908@linux.vnet.ibm.com>
On Thu, 30 Oct 2008 17:03:57 -0500
Jon Tollefson <kniht@linux.vnet.ibm.com> wrote:
> It was suggested by Andrew that using a macro that made an array
> look like a function call made it harder to understand the code.
> Cleaned up use of macro. We now reference the pgtable_cache array
> directly instead of using a macro.
I felt compelled to apply this. See http://en.wikipedia.org/wiki/Sunk_costs
to see why I am an irrational actor.
prev parent reply other threads:[~2008-11-04 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 22:03 [PATCH 1/1 v2] powerpc: hugetlb pgtable cache access cleanup Jon Tollefson
2008-11-04 21:32 ` Andrew Morton [this message]
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=20081104133231.fb224e68.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dwg@au1.ibm.com \
--cc=kniht@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nickpiggin@yahoo.com.au \
--cc=paulus@samba.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).