All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-kernel@vger.kernel.org
Cc: cpufreq@vger.kernel.org, davej@redhat.com,
	jonas.aberg@stericsson.com, martin.persson@stericsson.com,
	sundar.iyer@stericsson.com
Subject: [PATCH 10/12] drivers/cpufreq/db8500-cpufreq: remove references to cpu_*_map.
Date: Wed, 15 Feb 2012 15:28:04 +1030	[thread overview]
Message-ID: <1329281884.20530.rusty@rustcorp.com.au> (raw)

From: Rusty Russell <rusty@rustcorp.com.au>

This has been obsolescent for a while; time for the final push.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: Dave Jones <davej@redhat.com>
Cc: cpufreq@vger.kernel.org
Cc: Sundar Iyer <sundar.iyer@stericsson.com>
Cc: Martin Persson <martin.persson@stericsson.com>
Cc: Jonas Aaberg <jonas.aberg@stericsson.com>
---
 drivers/cpufreq/db8500-cpufreq.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/cpufreq/db8500-cpufreq.c b/drivers/cpufreq/db8500-cpufreq.c
--- a/drivers/cpufreq/db8500-cpufreq.c
+++ b/drivers/cpufreq/db8500-cpufreq.c
@@ -145,7 +145,7 @@ static int __cpuinit db8500_cpufreq_init
 	policy->cpuinfo.transition_latency = 20 * 1000; /* in ns */
 
 	/* policy sharing between dual CPUs */
-	cpumask_copy(policy->cpus, &cpu_present_map);
+	cpumask_copy(policy->cpus, cpu_present_mask);
 
 	policy->shared_type = CPUFREQ_SHARED_TYPE_ALL;
 


WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-kernel@vger.kernel.org
Cc: cpufreq@vger.kernel.org
Cc: davej@redhat.com
Cc: jonas.aberg@stericsson.com
Cc: martin.persson@stericsson.com
Cc: sundar.iyer@stericsson.com
Subject: [PATCH 10/12] drivers/cpufreq/db8500-cpufreq: remove references to cpu_*_map.
Date: Wed, 15 Feb 2012 15:28:04 +1030	[thread overview]
Message-ID: <1329281884.20530.rusty@rustcorp.com.au> (raw)

From: Rusty Russell <rusty@rustcorp.com.au>

This has been obsolescent for a while; time for the final push.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: Dave Jones <davej@redhat.com>
Cc: cpufreq@vger.kernel.org
Cc: Sundar Iyer <sundar.iyer@stericsson.com>
Cc: Martin Persson <martin.persson@stericsson.com>
Cc: Jonas Aaberg <jonas.aberg@stericsson.com>
---
 drivers/cpufreq/db8500-cpufreq.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/cpufreq/db8500-cpufreq.c b/drivers/cpufreq/db8500-cpufreq.c
--- a/drivers/cpufreq/db8500-cpufreq.c
+++ b/drivers/cpufreq/db8500-cpufreq.c
@@ -145,7 +145,7 @@ static int __cpuinit db8500_cpufreq_init
 	policy->cpuinfo.transition_latency = 20 * 1000; /* in ns */
 
 	/* policy sharing between dual CPUs */
-	cpumask_copy(policy->cpus, &cpu_present_map);
+	cpumask_copy(policy->cpus, cpu_present_mask);
 
 	policy->shared_type = CPUFREQ_SHARED_TYPE_ALL;
 


             reply	other threads:[~2012-02-15  4:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15  4:58 Rusty Russell [this message]
2012-02-15  4:58 ` [PATCH 10/12] drivers/cpufreq/db8500-cpufreq: remove references to cpu_*_map Rusty Russell
2012-02-15  9:23 ` Srivatsa S. Bhat

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=1329281884.20530.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=jonas.aberg@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.persson@stericsson.com \
    --cc=sundar.iyer@stericsson.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.