From: Rusty Russell <rusty@rustcorp.com.au>
To: Greg KH <greg@kroah.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: device_find broken in 2.6.11?
Date: Sat, 09 Jul 2005 01:36:04 +1000 [thread overview]
Message-ID: <1120836964.12218.63.camel@localhost.localdomain> (raw)
In-Reply-To: <20050708042922.GA4603@kroah.com>
On Thu, 2005-07-07 at 21:29 -0700, Greg KH wrote:
> On Fri, Jul 08, 2005 at 02:16:53PM +1000, Rusty Russell wrote:
> >
> > I was getting oopses in kset_find_obj when calling device_find in
> > 2.6.11.12.
>
> 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?
The xenbus code wants to find if a device is new: the Xen code is
currently against on 2.6.11.12.
Thanks!
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-07-08 15:36 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
2005-07-08 15:36 ` Rusty Russell [this message]
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=1120836964.12218.63.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox