linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: srivatsa.bhat@linux.vnet.ibm.com, mingo@kernel.org,
	tglx@linutronix.de, linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-numa@vger.kernel.org, Wen Congyang <wency@cn.fujitsu.com>
Subject: Re: [PATCH v2 2/2] Update sched_domains_numa_masks when new cpus are onlined.
Date: Thu, 04 Oct 2012 14:30:49 +0200	[thread overview]
Message-ID: <1349353849.14388.2.camel@twins> (raw)
In-Reply-To: <1348578751-16904-3-git-send-email-tangchen@cn.fujitsu.com>

On Tue, 2012-09-25 at 21:12 +0800, Tang Chen wrote:
> +static int sched_domains_numa_masks_update(struct notifier_block
> *nfb,
> +                                          unsigned long action,
> +                                          void *hcpu)
> +{
> +       int cpu = (int)hcpu; 

kernel/sched/core.c: In function ‘sched_domains_numa_masks_update’:
kernel/sched/core.c:6299:12: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]

I've changed it to:

	int cpu = (long)hcpu;




  reply	other threads:[~2012-10-04 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 13:12 [PATCH v2 0/2] Update sched_domains_numa_masks when new cpus are onlined Tang Chen
2012-09-25 13:12 ` [PATCH v2 1/2] Ensure sched_domains_numa_levels safe in other functions Tang Chen
2012-10-05 13:01   ` [tip:sched/urgent] sched: Ensure 'sched_domains_numa_levels' is safe to use " tip-bot for Tang Chen
2012-09-25 13:12 ` [PATCH v2 2/2] Update sched_domains_numa_masks when new cpus are onlined Tang Chen
2012-10-04 12:30   ` Peter Zijlstra [this message]
2012-10-05 13:02   ` [tip:sched/urgent] sched: Update sched_domains_numa_masks[][] " tip-bot for Tang Chen
2012-10-02 11:33 ` [PATCH v2 0/2] Update sched_domains_numa_masks " Peter Zijlstra

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=1349353849.14388.2.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-numa@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=wency@cn.fujitsu.com \
    --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;
as well as URLs for NNTP newsgroup(s).