From: Greg KH <greg@kroah.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: device_find broken in 2.6.11?
Date: Thu, 7 Jul 2005 21:29:22 -0700 [thread overview]
Message-ID: <20050708042922.GA4603@kroah.com> (raw)
In-Reply-To: <1120796213.12218.55.camel@localhost.localdomain>
On Fri, Jul 08, 2005 at 02:16:53PM +1000, Rusty Russell wrote:
> Hi Greg,
>
> I was getting oopses in kset_find_obj when calling device_find in
> 2.6.11.12. Noone else in the kernel uses device_find, but I couldnt'
> see anything wrong with it (mind you, I can't understand the
> kset_find_obj code to judge it).
>
> Iterating manually using bus_for_each_dev works though.
>
> Known problem?
Yup, there's a reason no one uses it. Use the version in 2.6.13-rc2, it
actually works.
What are you wanting to use it for?
thanks,
greg k-h
next prev parent reply other threads:[~2005-07-08 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 4:16 device_find broken in 2.6.11? Rusty Russell
2005-07-08 4:29 ` Greg KH [this message]
2005-07-08 15:36 ` Rusty Russell
2005-07-08 16:48 ` Greg KH
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=20050708042922.GA4603@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox