Date: Wed, 15 Apr 2009 19:48:06 -0700
From: Greg KH <greg@kroah.com>
To: David Vrabel <david.vrabel@csr.com>
Cc: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: device_for_each_child() before device_add() doesn't work
Message-ID: <20090416024806.GA4806@kroah.com>
References: <49E4BFD0.2020302@csr.com> <20090414165905.GA25645@kroah.com> <49E4D2FF.8090906@csr.com> <20090415051548.GC3462@kroah.com> <49E5F457.5090602@csr.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49E5F457.5090602@csr.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 830
Lines: 26

On Wed, Apr 15, 2009 at 03:51:03PM +0100, David Vrabel wrote:
> Greg KH wrote:
> > 
> > So the problem is for the first device being added, right?  Can't you
> > just have a flag for this?
> 
> It's trivial to fix in the UWB stack.

I'd recommend doing that :)

> >> This address must be assigned during initialization and during normal 
> >> operation and in the past we didn't need to special case the address 
> >> assignment during initialization.
> > 
> > Does the patch below fix the problem for you?
> 
> Yes.

Thanks for testing, I've now added the patch to my tree.

greg k-h
--
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/