public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add "bus" symlink to class/block devices
Date: Thu, 17 Feb 2005 13:35:31 -0800	[thread overview]
Message-ID: <20050217213531.GB15836@kroah.com> (raw)
In-Reply-To: <20050215220406.GA1419@vrfy.org>

On Tue, Feb 15, 2005 at 11:04:06PM +0100, Kay Sievers wrote:
> On Tue, Feb 15, 2005 at 09:53:44PM +0100, Kay Sievers wrote:
> > Add a "bus" symlink to the class and block devices, just like the "driver"
> > and "device" links. This may be a huge speed gain for e.g. udev to determine
> > the bus value of a device, as we currently need to do a brute-force scan in
> > /sys/bus/* to find this value.
> 
> Hmm, while playing around with it, I think we should create the "bus"
> link on the physical device on not on the class device.
> 
> Also the current "driver" link at the class device should be removed,
> cause class devices don't have a driver. Block devices never had this
> misleading symlink.
> 
> >From the class device we point with the "device" link to the physical
> device, and only the physical device should have the "driver" and the
> "bus" link, as it represents the real relationship.

Applied, thanks,

greg k-h

      parent reply	other threads:[~2005-02-17 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 20:53 [PATCH ] add "bus" symlink to class/block devices Kay Sievers
2005-02-15 22:04 ` [PATCH] " Kay Sievers
2005-02-15 22:25   ` Dmitry Torokhov
2005-02-15 23:44     ` Greg KH
2005-02-16  3:18       ` Dmitry Torokhov
2005-02-17 21:35   ` 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=20050217213531.GB15836@kroah.com \
    --to=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --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