mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, yinghai@kernel.org
Subject: Re: [PATCH] x86: use the same node_distance for 32 and 64-bit
Date: Sat, 24 Sep 2011 10:45:34 +0900	[thread overview]
Message-ID: <20110924014534.GY29319@htj.dyndns.org> (raw)
In-Reply-To: <201109191603.15560.hartleys@visionengravers.com>

On Mon, Sep 19, 2011 at 04:03:14PM -0700, H Hartley Sweeten wrote:
> The node_distance function is not x86 64-bit specific.  Having the #ifdef
> around the extern function declaration and the #define causes the default
> node_distance macro to be used in asm-generic/topology.h. This also causes
> a sparse warning in arch/x86/mm/numa.c when CONFIG_X86_64 is not set:
> 
> warning: symbol '__node_distance' was not declared. Should it be static?
> 
> Remove the #ifdef to fix both issues.
> 
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Yinghai Lu <yinghai@kernel.org>

Acked-by: Tejun Heo <tj@kernel.org>

Thank you.

-- 
tejun

      parent reply	other threads:[~2011-09-24  1:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19 23:03 H Hartley Sweeten
2011-09-20  0:51 ` David Rientjes
2011-10-14 20:27   ` David Rientjes
2011-12-05 12:44     ` Ingo Molnar
2011-12-06 20:22       ` [patch resend] " David Rientjes
2011-12-07  8:58         ` [tip:x86/asm] x86: Use " tip-bot for H Hartley Sweeten
2011-09-24  1:45 ` Tejun Heo [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=20110924014534.GY29319@htj.dyndns.org \
    --to=htejun@gmail.com \
    --cc=hartleys@visionengravers.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yinghai@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

all inboxes | Powered by JetHome®