From: Greg KH <greg@kroah.com>
To: Yu Zhao <yu.zhao@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v9 6/7] PCI: document SR-IOV sysfs entries
Date: Tue, 17 Feb 2009 23:19:16 -0800 [thread overview]
Message-ID: <20090218071916.GA15114@kroah.com> (raw)
In-Reply-To: <20090217170135.GA2520@yzhao-otc.sh.intel.com>
On Wed, Feb 18, 2009 at 01:01:35AM +0800, Yu Zhao wrote:
> On Wed, Feb 18, 2009 at 02:21:16PM +0800, Greg KH wrote:
> > On Tue, Feb 17, 2009 at 10:43:03PM +0800, Yu Zhao wrote:
> > > On Wed, Feb 18, 2009 at 11:49:10AM +0800, Greg KH wrote:
> > > > On Tue, Feb 17, 2009 at 08:50:21PM +0800, Yu Zhao wrote:
> > > > > I'd like to create a subdirectory under PCI device sysfs directory and
> > > > > put some symbol links into that directory (only symbol links). Should I
> > > > > use `device' or `kobject'? Currently I use `device' and get two extra
> > > > > file/directory (uevent and power) which look like useless for my case
> > > > > because this subdirectory doesn't reflect a real device.
> > > >
> > > > Neither, just use an attribute group, no new struct device should be
> > > > needed at all.
> > >
> > > Yes, I was thinking using an attribute group, however, it looks like we
> > > can't put symbol link into a group. Maybe I'm wrong, shed some light,
> > > please?
> >
> > Why would you want a symbolic link in an attribute group?
>
> Sorry I didn't make myself clear. I'd like to create a subdirectory (its
> parent is controlled by a `struct device') to only hold symbol links.
Ick. What would those links be to? And what are they for?
> Can I use an `attribute group' of the parent `struct device' for this,
> or a child `struct device', or a bare `struct kobject'?
You can't use an attribute group for symlinks.
You should use a struct device, but be careful, you are going to be
creating uevents that I don't think you really want to.
Care to describe what you are trying to do first?
thanks,
greg k-h
next prev parent reply other threads:[~2009-02-18 7:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 13:28 [PATCH v9 0/7] PCI: Linux kernel SR-IOV support Yu Zhao
2009-02-16 13:28 ` [PATCH v9 1/7] PCI: initialize and release SR-IOV capability Yu Zhao
2009-02-16 13:28 ` [PATCH v9 2/7] PCI: restore saved SR-IOV state Yu Zhao
2009-02-16 13:28 ` [PATCH v9 3/7] PCI: reserve bus range for SR-IOV device Yu Zhao
2009-02-16 13:28 ` [PATCH v9 4/7] PCI: add SR-IOV API for Physical Function driver Yu Zhao
2009-02-16 13:28 ` [PATCH v9 5/7] PCI: handle SR-IOV Virtual Function Migration Yu Zhao
2009-02-16 13:28 ` [PATCH v9 6/7] PCI: document SR-IOV sysfs entries Yu Zhao
2009-02-17 12:50 ` Yu Zhao
2009-02-17 13:01 ` Yu Zhao
2009-02-18 3:49 ` Greg KH
2009-02-17 14:43 ` Yu Zhao
2009-02-18 6:21 ` Greg KH
2009-02-17 17:01 ` Yu Zhao
2009-02-18 7:19 ` Greg KH [this message]
2009-02-17 19:21 ` Yu Zhao
2009-02-18 15:13 ` Greg KH
2009-02-16 13:28 ` [PATCH v9 7/7] PCI: manual for SR-IOV user and driver developer Yu Zhao
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=20090218071916.GA15114@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yu.zhao@intel.com \
/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