From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764781AbXGKVKk (ORCPT ); Wed, 11 Jul 2007 17:10:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762307AbXGKVKL (ORCPT ); Wed, 11 Jul 2007 17:10:11 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:53158 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762142AbXGKVKI (ORCPT ); Wed, 11 Jul 2007 17:10:08 -0400 Date: Wed, 11 Jul 2007 14:08:33 -0700 From: Greg KH To: Stefan Richter Cc: Yinghai Lu , Andrew Morton , Andi Kleen , rientjes@google.com, Christoph Lameter , Christoph Hellwig , David Miller , Linux Kernel Mailing List , netdev@vger.kernel.org Subject: Re: [PATCH 1/5] try parent numa_node at first before using default Message-ID: <20070711210833.GA22745@kroah.com> References: <200707101641.17672.yinghai.lu@sun.com> <200707101652.31378.yinghai.lu@sun.com> <4694B702.2050507@s5r6.in-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4694B702.2050507@s5r6.in-berlin.de> User-Agent: Mutt/1.5.15 (2007-04-06) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 11, 2007 at 12:54:58PM +0200, Stefan Richter wrote: > Yinghai Lu wrote: > > --- a/drivers/base/core.c > > +++ b/drivers/base/core.c > > @@ -547,6 +547,8 @@ static void klist_children_put(struct klist_node *n) > > > > void device_initialize(struct device *dev) > > { > > + int node; > > + > > kobj_set_kset_s(dev, devices_subsys); > > kobject_init(&dev->kobj); > > klist_init(&dev->klist_children, klist_children_get, > > @@ -557,7 +559,9 @@ void device_initialize(struct device *dev) > > spin_lock_init(&dev->devres_lock); > > INIT_LIST_HEAD(&dev->devres_head); > > device_init_wakeup(dev, 0); > > - set_dev_node(dev, -1); > > + > > + node = dev->parent ? dev_to_node(dev->parent) : -1; > > + set_dev_node(dev, node); > > } > > Two remarks: > > - device_add() is perhaps a better place to do this. Otherwise you > had to change code like drivers/input/gameport/gameport.c:: > gameport_init_port() which sets the parent device *after* the > call to device_initialize(). I agree, lots of code sets up the parent pointer after initialize and before add. One such example is the whole USB subsystem. Which makes me wonder how this code was really tested at all to show that it actually had an affect... So consider this patch series rejected from my side for now. thanks, greg k-h