From: Dave Hansen <haveblue@us.ibm.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Magnus Damm <magnus@valinux.co.jp>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] i386: srat and numaq cleanup
Date: Thu, 06 Oct 2005 07:56:25 -0700 [thread overview]
Message-ID: <1128610585.8401.15.camel@localhost> (raw)
In-Reply-To: <aec7e5c30510060329kb59edagb619f00b8a58bf3e@mail.gmail.com>
On Thu, 2005-10-06 at 19:29 +0900, Magnus Damm wrote:
> On 10/6/05, Dave Hansen <haveblue@us.ibm.com> wrote:
> > I'm highly suspicious of any "cleanup" that adds more code than it
> > deletes. What does this clean up?
>
> The patch removes #ifdefs from get_memcfg_numa() and introduces an
> inline get_zholes_size(). The #ifdefs are moved down one level to the
> files srat.h and numaq.h and empty inline functions are added. These
> empty inline function are probably the reason for the added lines.
It does remove two #ifdefs, but it adds two #else blocks in other
places.
I also noticed that acpi20_parse_srat() can fail. So, has_srat may
belong in that function, not in get_memcfg_from_srat()
Why ever have this block?
> + if ((ret = get_zholes_size_numaq(nid)))
> + return ret;
get_zholes_size_numaq() is *ALWAYS* empty/false, right? There's no need
to have a stub for it.
-- Dave
--
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:[~2005-10-06 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 8:39 Magnus Damm
2005-10-05 16:37 ` Dave Hansen
2005-10-06 10:29 ` Magnus Damm
2005-10-06 14:56 ` Dave Hansen [this message]
2005-10-07 7:54 ` Magnus Damm
2005-10-07 13:28 ` Dave Hansen
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=1128610585.8401.15.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=magnus.damm@gmail.com \
--cc=magnus@valinux.co.jp \
/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