LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Greg KH <greg@kroah.com>, Kay Sievers <kay.sievers@vrfy.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: No more "device" symlinks for classes
Date: Sun, 14 Jan 2007 00:51:37 +0100	[thread overview]
Message-ID: <45A97089.5090004@drzeus.cx> (raw)

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.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

             reply	other threads:[~2007-01-13 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 23:51 Pierre Ossman [this message]
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

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=45A97089.5090004@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --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).