linux-kernel - Re: device_for_each_child() before device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090416024806.GA4806@kroah.com>
Date:	Wed, 15 Apr 2009 19:48:06 -0700
From:	Greg KH <greg@...ah.com>
To:	David Vrabel <david.vrabel@....com>
Cc:	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: device_for_each_child() before device_add() doesn't work

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/