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

On Tue, May 03, 2011 at 08:38:48AM -0400, Robert P. J. Day wrote:
> On Tue, 3 May 2011, Greg KH wrote:
> 
> > On Tue, May 03, 2011 at 07:45:54AM -0400, Robert P. J. Day wrote:
> > >   once you see that living, breathing example, what more would you
> > > need to know about how to have your module/driver create a simple
> > > read-only proc file?
> >
> > You need to know that if your module/driver ever creates a simple
> > read-only proc file, they will be flamed to a crisp on lkml when
> > they submit it :)
> >
> > Seriously, don't ever create a new proc file, it's not anything
> > anyone should ever be doing anymore.
> 
>   so have proc/seq file been massively deprecated in favour of sysfs
> attribute files, then?

Yes, that happened about 8 years ago :)

No driver should ever add a proc file, it's that simple.

thanks,

greg k-h