Date: Wed, 14 Dec 2005 16:10:18 -0800
From: Pete Zaitcev <zaitcev@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, katzj@redhat.com, zaitcev@redhat.com
Subject: Re: "block" symlink in sysfs for a multifunction device
Message-Id: <20051214161018.254e75bb.zaitcev@redhat.com>
In-Reply-To: <20051214234255.GA3275@kroah.com>
References: <20051212134904.225dcc5d.zaitcev@redhat.com>
	<20051214055019.GA23036@kroah.com>
	<20051214152615.13b6b105.zaitcev@redhat.com>
	<20051214234255.GA3275@kroah.com>
Organization: Red Hat, Inc.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 772
Lines: 19

On Wed, 14 Dec 2005 15:42:55 -0800, Greg KH <greg@kroah.com> wrote:

> And if this isn't acceptable, what would be?
> 
> Just because kudzu is messed up... :)

I thought maybe creating some struct kobject by hand for every LUN.
This is undesirable mainly because I do not trust myself with handling
struct kobject at all (currently I only use block device API and so I
blame Jens every time there's a problem :-)). But if Jeremy cannot
work around it, I would have to think about it - maybe as a Fedora-specific
patch.

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/