From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-next@vger.kernel.org, Mike Travis <travis@sgi.com>
Subject: linux-next: manual merge of the cpus4096 tree
Date: Mon, 7 Jul 2008 16:20:10 +1000 [thread overview]
Message-ID: <20080707162010.58305a91.sfr@canb.auug.org.au> (raw)
Hi all,
Today's linux-next merge of the cpus4096 tree needed the fixup below. As
you know, Linus' tree now has trivial definitions of next_cpu_nr,
cpus_weight_nr and for_each_cpu_mask_nr. The merge mechanics did not
notice this automatically so I had to remove the old definitions from
cpumask.h.
It would be nice if you could do the merge with Linus' tree
yourself and fix this within the cpus4096 tree tree.
Also, it would be nice if some of the other subsystems that need changing
could be sent the patches to do that. It would reduce the conflicts in
linux-next and during the merge window for Linus.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
>From 0b848f997ba0ef132356c829114d898e0a51c045 Mon Sep 17 00:00:00 2001
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 7 Jul 2008 15:59:04 +1000
Subject: [PATCH] cpumask: fixup API change merge
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
include/linux/cpumask.h | 4 ----
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/include/linux/cpumask.h b/include/linux/cpumask.h
index 47418b1..80226e7 100644
--- a/include/linux/cpumask.h
+++ b/include/linux/cpumask.h
@@ -394,10 +394,6 @@ int __next_cpu_nr(int n, const cpumask_t *srcp);
#endif /* NR_CPUS > 64 */
-#define next_cpu_nr(n, src) next_cpu(n, src)
-#define cpus_weight_nr(cpumask) cpus_weight(cpumask)
-#define for_each_cpu_mask_nr(cpu, mask) for_each_cpu_mask(cpu, mask)
-
/*
* The following particular system cpumasks and operations manage
* possible, present and online cpus. Each of them is a fixed size
--
1.5.6
next reply other threads:[~2008-07-07 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 6:20 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 2:47 linux-next: manual merge of the cpus4096 tree Stephen Rothwell
2008-09-12 5:18 Stephen Rothwell
2009-01-19 1:08 Stephen Rothwell
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=20080707162010.58305a91.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=travis@sgi.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