linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: bug report: wait_for_sysfs video0
Date: Sat, 16 Oct 2004 21:48:19 +0000	[thread overview]
Message-ID: <20041016214819.GA1621@vrfy.org> (raw)
In-Reply-To: <20041016085957.GB3981@fjellstad.org>

On Sat, Oct 16, 2004 at 02:30:40PM -0700, John L Fjellstad wrote:
> On Sat, Oct 16, 2004 at 06:36:04PM +0200, Kay Sievers wrote:
> 
> > This seems like a problem with your device driver. There should be a
> > symlink to the physical device. Please bug the driver maintainer to
> > create the "device" and "driver" symlink in the class device, as
> > hardware/userspace integration depends on proper sysfs use.
> 
> How do I find out who the maintainer is?  Or do I just post to the
> kernel list?

What kernel module drives your hardware? Or what kind of hardware is it?

Kay



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-10-16 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-16  8:59 bug report: wait_for_sysfs video0 John L Fjellstad
2004-10-16 16:36 ` Kay Sievers
2004-10-16 21:30 ` John L Fjellstad
2004-10-16 21:48 ` Kay Sievers [this message]
2004-10-16 22:10 ` John L Fjellstad
2004-10-17  0:37 ` Kay Sievers

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=20041016214819.GA1621@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).