From mboxrd@z Thu Jan 1 00:00:00 1970 From: greg@kroah.com (Greg KH) Date: Wed, 23 Aug 2017 15:57:05 -0700 Subject: Don't know where to start linux kernel programming In-Reply-To: References: <96047b43-7bb5-0328-e5ac-a972dacd391f@partner.samsung.com> <10334.1503421171@turing-police.cc.vt.edu> <20170822173912.GA1350@kroah.com> Message-ID: <20170823225705.GB5193@kroah.com> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Wed, Aug 23, 2017 at 09:06:49PM +0530, Umair Khan wrote: > Hi Greg, > > On Tue, Aug 22, 2017 at 11:09 PM, Greg KH wrote: > > On Tue, Aug 22, 2017 at 12:59:31PM -0400, valdis.kletnieks at vt.edu wrote: > >> On Tue, 22 Aug 2017 12:48:42 -0400, Cindy-Sue Causey said: > >> > >> > An observation that may just mean I haven't stumbled upon it yet is > >> > that it would be nice to... stumble upon... a list of kernel problems > >> > that *kernelnewbies* could cut their teeth on. I do understand that > >> > this is a naive wish list item due to the nearly every nanosecond > >> > changing complexity of things. :) > >> > >> Such a thing existed 10 or 15 years ago. Unfortunately for the newbies, there > >> are very few problems that newbies can attack, because if they were that > >> simple, somebody would already have *done* them. > > > > Not really, please look at drivers/staging/*/TODO there are loads of > > simple things left to do, with more being added all the time (a huge new > > wireless driver just landed that could use lots of cleanups.) > > Which wireless driver exactly? The "new" one in the linux-next tree (it's also in the staging-next branch of the staging.git tree on git.kernel.org). Don't remember the exact name, it should be easy to find...