Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761254AbZFJRDi (ORCPT ); Wed, 10 Jun 2009 13:03:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761080AbZFJRDG (ORCPT ); Wed, 10 Jun 2009 13:03:06 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:52462 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761022AbZFJRDE (ORCPT ); Wed, 10 Jun 2009 13:03:04 -0400 Date: Wed, 10 Jun 2009 19:01:58 +0200 From: Ingo Molnar To: Dave Jones , Rusty Russell , Yinghai Lu , Avi Kivity , Linus Torvalds , Andrew Morton , Thomas Gleixner , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , cpufreq@vger.kernel.org Subject: Re: [PATCH 4/6] x86/cpufreq: use cpumask_copy instead of = Message-ID: <20090610170158.GB31096@elte.hu> References: <4A2835D8.6040903@kernel.org> <200906091627.45411.rusty@rustcorp.com.au> <4A2E19A7.1000302@kernel.org> <200906101350.23594.rusty@rustcorp.com.au> <20090610133952.GA10334@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090610133952.GA10334@redhat.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1447 Lines: 36 * Dave Jones wrote: > On Wed, Jun 10, 2009 at 01:50:22PM +0930, Rusty Russell wrote: > > On Tue, 9 Jun 2009 05:43:27 pm Yinghai Lu wrote: > > > Rusty Russell wrote: > > > > On Sun, 7 Jun 2009 07:23:52 am Yinghai Lu wrote: > > > >> so later could use nr_cpumask_bits in cpumask_size when MAXSMP is used > > > > > > > > I have a (more ambitious) patch for this in my queue, which weans it off > > > > this entirely: > > > > > > > > Subject: cpumask: avoid playing with cpus_allowed in powernow-k8.c > > ... > > > will be in .31? > > > > Hope so, it's been in linux-next for ages. The cpufreq > > maintainers seem to take a relaxed approach to patches, FWIW. > > With so much of the cpumask stuff going through Ingo's trees, I've > taken the approach that it's easier to just let it continue to do > so rather than cherry picking the occasional cpufreq touching > part. Well, now that the main (and most risky) cpumask changes are over and done, it would be nice to go back to the regular model. Overlap in trees frequently causes bugs, friction and general unhappiness. There's nothing cpufreq related pending in any of the -tip trees in this cycle. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/