From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Tue, 3 May 2011 07:11:32 -0700
Subject: looking for simple module/driver programming examples in source
	tree
In-Reply-To: <alpine.DEB.2.00.1105030942020.9448@localhost6.localdomain6>
References: <alpine.DEB.2.00.1105030734250.7346@localhost6.localdomain6>
	<20110503122800.GA24483@kroah.com>
	<alpine.DEB.2.00.1105030837450.8195@localhost6.localdomain6>
	<20110503125425.GA29202@kroah.com>
	<alpine.DEB.2.00.1105030857570.8315@localhost6.localdomain6>
	<BANLkTimvDf6rOtwZu0QFe9dpBQCO_5nCwA@mail.gmail.com>
	<alpine.DEB.2.00.1105030942020.9448@localhost6.localdomain6>
Message-ID: <20110503141132.GA8056@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Tue, May 03, 2011 at 09:44:47AM -0400, Robert P. J. Day wrote:
> p.s.  on that note, of course, i'm interested in really simple
> examples of drivers that create increasingly complex collections of
> sysfs attr files.  i *really* like to explain stuff like this by being
> able to point at existing drivers in the tree.

Any of the sensor drivers would be good examples of this, they create
loads of sysfs files.

Also please explain that _any_ new sysfs or file that is added, a
corresponding Documentation/ABI/ file needs to be also added.

thanks,

greg k-h