LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Greg KH" <greg@kroah.com>
Cc: "Andrey Borzenkov" <arvidjaar@mail.ru>,
	"Pierre Ossman" <drzeus-list@drzeus.cx>,
	linux-kernel@vger.kernel.org
Subject: Re: No more "device" symlinks for classes
Date: Sun, 14 Jan 2007 09:46:02 +0100	[thread overview]
Message-ID: <3ae72650701140046p5c3280a1ofd7b59cece11b773@mail.gmail.com> (raw)
In-Reply-To: <20070114073937.GA10585@kroah.com>

On 1/14/07, Greg KH <greg@kroah.com> wrote:
> On Sun, Jan 14, 2007 at 09:10:59AM +0300, Andrey Borzenkov wrote:
> > Pierre Ossman wrote:
> >
> > > Hi guys,
> > >
> > > I just wanted to know the rationale behind
> > > 99ef3ef8d5f2f5b5312627127ad63df27c0d0d05 (no more "device" symlink in
> > > class devices). I thought that was a rather convenient way of finding
> > > which physical device the class device was coupled to.
> > >
> >
> > Actually I wonder why those links still present even when I told system not
> > to create them?
> >
> > {pts/1}% grep DEPRE /boot/config
> > # CONFIG_SYSFS_DEPRECATED is not set
> > # CONFIG_PM_SYSFS_DEPRECATED is not set
> > {pts/1}% find /sys/class -name device
> > /sys/class/pcmcia_socket/pcmcia_socket2/device
> > /sys/class/pcmcia_socket/pcmcia_socket1/device
> > /sys/class/pcmcia_socket/pcmcia_socket0/device
> > /sys/class/usb_device/usbdev1.1/device
> > /sys/class/usb_host/usb_host1/device
> > /sys/class/scsi_disk/0:0:0:0/device
> > /sys/class/scsi_device/1:0:0:0/device
> > /sys/class/scsi_device/0:0:0:0/device
> > /sys/class/scsi_host/host1/device
> > /sys/class/scsi_host/host0/device
> > /sys/class/net/eth0/device
> > /sys/class/net/eth1/device
> > /sys/class/input/input1/ts0/device
> > /sys/class/input/input1/mouse0/device
> > /sys/class/input/input1/event1/device
> > /sys/class/input/input1/device
> > /sys/class/input/input0/event0/device
> > /sys/class/input/input0/device
> > {pts/1}% uname -a
> > Linux cooker 2.6.20-rc5-1avb #10 Sat Jan 13 14:05:34 MSK 2007 i686 Pentium
> > III (Coppermine) GNU/Linux
>
> Because I haven't finished converting all of the different usages of
> struct class_device to struct device just yet.  When that happens, those
> links go away, as the /sys/class/foo_class/foo is a symlink itself into
> the /sys/devices/ tree.

Right, you only told not to create the links for already converted
subsystems to create the class-devices in /sys/devices. You can never
supress the links for subsystems which still create device-directories
in /sys/class, because you would lose the parent information then and
udev and HAL couldn't work anymore.

Kay
Kay

      reply	other threads:[~2007-01-14  8:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 23:51 Pierre Ossman
2007-01-14  0:02 ` Kay Sievers
2007-01-14  0:29   ` Pierre Ossman
2007-01-14  0:35     ` Kay Sievers
2007-01-14  6:10 ` Andrey Borzenkov
2007-01-14  7:39   ` Greg KH
2007-01-14  8:46     ` Kay Sievers [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=3ae72650701140046p5c3280a1ofd7b59cece11b773@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=arvidjaar@mail.ru \
    --cc=drzeus-list@drzeus.cx \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: No more "device" symlinks for classes' \
    /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

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).