From: me@tobin.cc (Tobin C. Harding)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Don't know where to start linux kernel programming
Date: Fri, 25 Aug 2017 12:34:37 +1000 [thread overview]
Message-ID: <20170825023437.GA10042@eros> (raw)
In-Reply-To: <20170823225705.GB5193@kroah.com>
On Wed, Aug 23, 2017 at 03:57:05PM -0700, Greg KH wrote:
> 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 <greg@kroah.com> 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...
looks like it may be drivers/staging/rtlwifi
next prev parent reply other threads:[~2017-08-25 2:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170822105248epcas1p1dc4605938a18403f1af939a0ea7bcf14@epcas1p1.samsung.com>
2017-08-22 10:52 ` Don't know where to start linux kernel programming SUNIL KHORWAL
2017-08-22 11:14 ` Kamil Konieczny
2017-08-22 11:15 ` SUNIL KHORWAL
2017-08-22 22:52 ` Tobin C. Harding
2017-08-22 16:48 ` Cindy-Sue Causey
2017-08-22 16:59 ` valdis.kletnieks at vt.edu
2017-08-22 17:39 ` Greg KH
2017-08-23 15:36 ` Umair Khan
2017-08-23 22:57 ` Greg KH
2017-08-25 2:34 ` Tobin C. Harding [this message]
2017-08-23 20:08 ` Ruben Safir
2017-08-23 22:56 ` Greg KH
2017-08-22 23:26 ` Greg Freemyer
2017-08-23 9:34 ` Ruben Safir
2017-08-23 12:24 ` Daniel.
2017-08-23 23:46 ` Greg Freemyer
2017-08-24 0:03 ` Ruben Safir
2017-08-24 0:23 ` Greg Freemyer
2017-08-24 0:46 ` Greg KH
2017-08-24 1:56 ` Ruben Safir
2017-08-22 15:04 ` valdis.kletnieks at vt.edu
2017-08-22 22:55 ` Tobin C. Harding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170825023437.GA10042@eros \
--to=me@tobin.cc \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).