linux-kernel - Re: [RFC PATCH 2/7] include/linux: add headers for drivers/zio

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:	Wed, 30 Nov 2011 15:21:04 +0900
From:	Greg KH <greg@...ah.com>
To:	Federico Vaga <federico.vaga@...il.com>
Cc:	Alessandro Rubini <rubini@...dd.com>, linux-iio@...r.kernel.org,
	linux-kernel@...r.kernel.org, dcobas@...n.ch, siglesia@...n.ch,
	manohar.vanga@...n.ch
Subject: Re: [RFC PATCH 2/7] include/linux: add headers for drivers/zio

On Mon, Nov 28, 2011 at 03:56:45PM +0100, Federico Vaga wrote:
> I don't reply to each point because I suppose the point is: "kobject
> or device for sysfs?", maybe I misunderstood.

That is correct.

> I know that it is not a good thing reply with a new question, but I
> think it can clarify the problem.
> 
> Why device is it preferred to export some sysfs attributes when sysfs
> ask me kobject?

If your code is working properly, you don't have to ever make sysfs
calls, only driver core calls, for sysfs files.  There might be a few
minor exceptions, but I think the coverage is all there now.

> As I tested both device and kobject, I'll do a parallel implementation
> with device.

As you are using a tree of devices, please use struct device, I can't
accept the code otherwise.

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/