linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevinfo patch
Date: Fri, 26 Mar 2004 12:50:57 +0000	[thread overview]
Message-ID: <20040326133632.GA9525@in.ibm.com> (raw)
In-Reply-To: <20040323215101.GA30721@us.ibm.com>

On Fri, Mar 26, 2004 at 11:24:39AM +0100, Kay Sievers wrote:
> On Fri, Mar 26, 2004 at 11:21:29AM +0500, Ananth N Mavinakayanahalli wrote:
> > On Fri, Mar 26, 2004 at 04:47:35AM +0100, Kay Sievers wrote:
> > > On Fri, Mar 26, 2004 at 01:26:46AM +0100, Carl-Daniel Hailfinger wrote:
> > > > Greg KH wrote:
> > > > > On Tue, Mar 23, 2004 at 01:51:01PM -0800, Daniel Stekloff wrote:
> > > 
> > > No, it breaks the net device handling. I think we should change
> > > libsysfs instead, not to return a class device for '/block', if
> > > we want to fix it.
> > 
> > /sys/block is considered a sysfs "class" and not a class_device. So, 
> > going by udevinfo's help, -p expects path to a class_device and _not_ 
> > a class itself and hence option /sys/block with -p is not a valid query. 
> > 
> > Kay?
> 
> Yes, it's invalid, but we shouldn't print major minor for a invalid
> path. sysfs_open_class_device_path("/block") returns a device. If this is
> the right behavior for libsysfs, I will change the get_device_type("/block")
> not to return a 'b'-type.

Libsysfs validates the path given to it for opening a class_device to be
a valid directory; it does not however validate if the path is a valid
class_device path. So, in the case of udevinfo, a 'b' type should not 
be returned if the path is just /sys/block or /sys/block/


Thanks,
Ananth



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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-03-26 12:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 21:51 udevinfo patch Daniel Stekloff
2004-03-23 22:42 ` Kay Sievers
2004-03-24 17:49 ` Greg KH
2004-03-26  0:26 ` Carl-Daniel Hailfinger
2004-03-26  3:47 ` Kay Sievers
2004-03-26  5:25 ` Carl-Daniel Hailfinger
2004-03-26  5:35 ` Ananth N Mavinakayanahalli
2004-03-26 10:15 ` Kay Sievers
2004-03-26 10:24 ` Kay Sievers
2004-03-26 12:50 ` Ananth N Mavinakayanahalli [this message]
2004-03-26 16:43 ` Carl-Daniel Hailfinger
2004-03-26 17:19 ` Kay Sievers
2004-03-31 23:00 ` 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=20040326133632.GA9525@in.ibm.com \
    --to=ananth@in.ibm.com \
    --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).