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
Date: Wed, 15 Apr 2009 19:48:06 -0700 [thread overview]
Message-ID: <20090416024806.GA4806@kroah.com> (raw)
In-Reply-To: <49E5F457.5090602@csr.com>
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
prev parent reply other threads:[~2009-04-16 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 16:54 device_for_each_child() before device_add() doesn't work David Vrabel
2009-04-14 16:59 ` Greg KH
2009-04-14 18:16 ` David Vrabel
2009-04-15 5:15 ` Greg KH
2009-04-15 14:51 ` David Vrabel
2009-04-16 2:48 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090416024806.GA4806@kroah.com \
--to=greg@kroah.com \
--cc=david.vrabel@csr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.