From: Greg KH <greg@kroah.com>
To: akpm@digeo.com
Cc: linux-kernel@vger.kernel.org, Patrick Mochel <mochel@osdl.org>
Subject: problem with sysfs symlink "fix"
Date: Mon, 19 May 2003 17:10:52 -0700 [thread overview]
Message-ID: <20030520001052.GA28067@kroah.com> (raw)
In the latest -bk tree sysfs's symlinks are a bit messed up:
$ tree /sys/bus/pci/
/sys/bus/pci/
|-- devices
| |-- 00:00.0 -> ../../../
| |-- 00:01.0 -> ../../../
| |-- 00:1d.0 -> ../../../
| |-- 00:1d.1 -> ../../../
| |-- 00:1d.7 -> ../../../
| |-- 00:1e.0 -> ../../../
| |-- 00:1f.0 -> ../../../
| |-- 00:1f.1 -> ../../../
| |-- 00:1f.3 -> ../../../
| |-- 00:1f.5 -> ../../../
| |-- 02:03.0 -> ../../../
| |-- 02:04.0 -> ../../../
| `-- 02:05.0 -> ../../../
`-- drivers
|-- PIIX IDE
| `-- 00:1f.1 -> ../../../../
|-- aic7xxx
| `-- 02:05.0 -> ../../../../
|-- eepro100
|-- ehci-hcd
| `-- 00:1d.7 -> ../../../../
|-- intel810_audio
| `-- 00:1f.5 -> ../../../../
|-- ohci-hcd
|-- parport_pc
|-- serial
|-- tg3
| `-- 02:03.0 -> ../../../../
`-- uhci-hcd
|-- 00:1d.0 -> ../../../../
`-- 00:1d.1 -> ../../../../
Could your fix to fs/sysfs/symlink.c have caused this?
thanks,
greg k-h
next reply other threads:[~2003-05-19 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 0:10 Greg KH [this message]
2003-05-20 7:13 ` problem with sysfs symlink "fix" Andrew Morton
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=20030520001052.GA28067@kroah.com \
--to=greg@kroah.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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