From: Greg KH <greg@kroah.com>
To: Matthew Wilcox <matthew@wil.cx>,
Douglas Gilbert <dougg@torque.net>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: lsscsi-0.17 released
Date: Wed, 22 Feb 2006 10:32:26 -0800 [thread overview]
Message-ID: <20060222183226.GA12542@kroah.com> (raw)
In-Reply-To: <20060222180015.GB20880@merlin.emma.line.org>
On Wed, Feb 22, 2006 at 07:00:15PM +0100, Matthias Andree wrote:
> On Wed, 22 Feb 2006, Greg KH wrote:
>
> > It was changed as there would be more than one "block" symlink in a
> > device's directory if more than one block device was attached to a
> > single struct device. For example, ub and multi-lun devices (there were
> > other reports of this happening for scsi devices too at the time from
> > what I remember.)
>
> OK, just post an announcement to l-k when sysfs has stabilized enough to
> be worth bothering.
Um, this was a "bugfix". The kernel was creating multiple symlinks with
the same name, in the same directory, pointing to different locations.
How do you expect us to fix that in a format that does not change the
name of the symlink?
People sure are grumpy this morning...
greg k-h
next prev parent reply other threads:[~2006-02-22 18:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 23:39 lsscsi-0.17 released Douglas Gilbert
2006-02-22 8:50 ` Matthias Andree
2006-02-22 15:01 ` Douglas Gilbert
2006-02-22 16:06 ` Matthias Andree
2006-02-22 16:27 ` Douglas Gilbert
2006-02-22 16:34 ` Matthew Wilcox
2006-02-22 16:38 ` Randy.Dunlap
2006-02-22 17:14 ` Greg KH
2006-02-22 18:00 ` Matthias Andree
2006-02-22 18:32 ` Greg KH [this message]
2006-02-22 20:22 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2006-02-22 17:59 Douglas Gilbert
2006-02-22 18:37 ` 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=20060222183226.GA12542@kroah.com \
--to=greg@kroah.com \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.