Messages in this thread | | | Date | Fri, 07 Nov 2008 10:17:03 -0800 | From | Mike Travis <> | Subject | Re: [PATCH] cpumask: introduce new API, without changing anything |
| |
Ingo Molnar wrote: ... > Find below the delta patch between the two versions, and an > analysis/review of the changes. I've started testing it as well, and > it's looking good so far. > ... > "0c82f41: cpumask:new-API-only" thus has only a couple of hours of > lifetime and the "this has been in linux-next" is only true for that > short time period. > > So ... i've reconstructed what's new in 0c82f41, and i came up with > the delta patch below. ... >>From cd83e42c6b0413dcbb548c2ead799111ff7e6a13 Mon Sep 17 00:00:00 2001 > From: Rusty Russell <rusty@rustcorp.com.au> > Date: Fri, 7 Nov 2008 11:12:29 +1100 > Subject: [PATCH] cpumask: new API, v2 > > - add cpumask_of() > - add free_bootmem_cpumask_var() ...
I'd like to begin resubmitting the patches that were in the cpus4096-v2 branch but I'm not quite sure how to set up the git tree. I have:
git-remote add linus git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git git-remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git git-remote update git-checkout -b cpus4096 tip/cpus4096
But I don't see the linux-next changes (like cpumask_first for uniprocessor), so I'm guessing I need to either merge in linux-next, or insert it into the above setup commands?
Fyi, hopefully this patch submission conduit will work:
generic only: via linux-next arch-specific (x86 + others): Rusty via arch-maintainers (linux-next?) (x86 only): Mike via tip/cpus4096
Does this work for you?
Thanks, Mike
| |