lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 17 Feb 2009 19:49:10 -0800
From:	Greg KH <greg@...ah.com>
To:	Yu Zhao <yu.zhao@...el.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 6/7] PCI: document SR-IOV sysfs entries

On Tue, Feb 17, 2009 at 08:50:21PM +0800, Yu Zhao wrote:
> Hi Greg,
> 
> The `struct device' is preferred over the `struct kobject' in all cases
> that create subdirectory in sysfs, is this true?

If you have a parent directory being controlled by a struct device, yes.

> 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.

thanks,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ