From: Andrew Morton <akpm@linux-foundation.org>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: "rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Venkatesh Pallipadi <venki@google.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Mike Travis <travis@sgi.com>,
"Paul E. McKenney" <paul.mckenney@linaro.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Gilad Ben-Yossef <gilad@benyossef.com>
Subject: Re: [PATCH v2] arch/ia64: remove references to cpu_*_map.
Date: Wed, 15 Feb 2012 13:02:40 -0800 [thread overview]
Message-ID: <20120215130240.7308f373.akpm@linux-foundation.org> (raw)
In-Reply-To: <4F3B8EAE.4050809@linux.vnet.ibm.com>
On Wed, 15 Feb 2012 16:23:34 +0530
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com> wrote:
> This patch ought to go along with the patchsets that do cleanups in other
> architectures as well.. And it looks like Rusty's patchset[1] is a superset of
> Venki's patchset[2].. So, Rusty, would you kindly take this patch into your
> patchset? (It should come before the 11/12 in your patchset. This should apply
> at that point easily, because I have modified it to suit your 11/12 which also
> touches ia64).
OK, I'm officially all confused. I think I'll drop everything and wait
until it settles down. Please, someone prepare a single patch series.
The cpumask-related patches whcih I'm currently holding are:
smp-introduce-a-generic-on_each_cpu_mask-function.patch
#arm-move-arm-over-to-generic-on_each_cpu_mask.patch: fold
arm-move-arm-over-to-generic-on_each_cpu_mask.patch
#tile-move-tile-to-use-generic-on_each_cpu_mask.patch: fold
tile-move-tile-to-use-generic-on_each_cpu_mask.patch
smp-add-func-to-ipi-cpus-based-on-parameter-func.patch
smp-add-func-to-ipi-cpus-based-on-parameter-func-fix.patch
smp-add-func-to-ipi-cpus-based-on-parameter-func-update.patch
smp-add-func-to-ipi-cpus-based-on-parameter-func-update-fix.patch
smp-add-func-to-ipi-cpus-based-on-parameter-func-v9.patch
smp-add-func-to-ipi-cpus-based-on-parameter-func-v9-fix.patch
slub-only-ipi-cpus-that-have-per-cpu-obj-to-flush.patch
fs-only-send-ipi-to-invalidate-lru-bh-when-needed.patch
mm-only-ipi-cpus-to-drain-local-pages-if-they-exist.patch
mm-only-ipi-cpus-to-drain-local-pages-if-they-exist-update.patch
mm-only-ipi-cpus-to-drain-local-pages-if-they-exist-v9.patch
#
arch-ia64-remove-references-to-cpu__map.patch
cpumask-avoid-mask-based-num_possible_cpus-and-num_online_cpus.patch
So I'm thinking the thing to do is to drop just the final two?
next prev parent reply other threads:[~2012-02-15 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 10:53 [PATCH v2] arch/ia64: remove references to cpu_*_map Srivatsa S. Bhat
2012-02-15 21:02 ` Andrew Morton [this message]
2012-02-15 23:10 ` Rusty Russell
2012-02-16 1:58 ` Venki Pallipadi
2012-02-16 2:32 ` Andrew Morton
2012-02-19 22:44 ` Rusty Russell
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=20120215130240.7308f373.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=gilad@benyossef.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paul.mckenney@linaro.org \
--cc=rjw@sisk.pl \
--cc=rusty@rustcorp.com.au \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tony.luck@intel.com \
--cc=travis@sgi.com \
--cc=venki@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox