All of lore.kernel.org
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Work
Date: Fri, 25 Jul 2014 08:17:21 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407250814270.6376@localhost> (raw)
In-Reply-To: <CAJyon0vSm2qAuNS=3BOikF-4GAVit6yD8irqFaoPHHnnng7ZXA@mail.gmail.com>

On Fri, 25 Jul 2014, Lucas Tanure wrote:

> Hi,?
> Watch :?http://www.youtube.com/watch?v=LLBrBBImJt4
>
> Read :?
> http://kernelnewbies.org/OPWfirstpatch
> http://kernelnewbies.org/KernelBuild?
> http://lwn.net/Articles/571980/
>
> Goal : Clone, build and run linux-next.?
>
> After that you can look for how to clean up a?staging driver.

  if i may (since i'm sure i antagonized my share of kernel gurus once
upon a time as i was getting my feet wet), start with cleaning up the
docs. read up on a subsystem, peruse the code, check the comments, see
if there's accompanying explanation in the Documentation/ directory,
and either correct obvious mistakes or improve what's there. the
obvious advantage to this is that you can't break stuff by working on
documentation. and everyone wants better documentation.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2014-07-25 12:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 16:38 Work Nick Krause
2014-07-24 16:43 ` Work Kristofer Hallin
2014-07-24 16:44 ` Work Lucas Tanure
2014-07-24 16:47   ` Work Nick Krause
2014-07-26 21:13   ` Work Yi Li
2014-07-26 21:55     ` Work Lucas Tanure
2014-07-24 16:51 ` Work Andev
2014-07-24 17:10   ` Work Nick Krause
2014-07-25  2:23     ` Work Nick Krause
2014-07-25  5:33       ` Work ravi ranjan Mishra
2014-07-25 11:44         ` Work Lucas Tanure
2014-07-25 12:17           ` Robert P. J. Day [this message]
2014-07-25 15:19             ` Work Nick Krause
2014-07-25 17:18               ` Work Robert P. J. Day
2014-07-25 17:28         ` Work Valdis.Kletnieks at vt.edu
2014-07-25 17:42       ` Work Valdis.Kletnieks at vt.edu
2014-07-25 21:54         ` Work Nick Krause
2014-07-25 22:23           ` Work Arlie Stephens
2014-07-25 23:02             ` Work Nick Krause
2014-07-25 23:35             ` Work Valdis.Kletnieks at vt.edu
2014-07-25 23:44               ` Work Nick Krause
2014-07-26  1:08               ` Work (really slow directory access on ext4) Arlie Stephens
2014-07-26  1:22                 ` Nick Krause
2014-07-30  2:34                   ` Nick Krause
2014-07-30 17:38                     ` Arlie Stephens
2014-07-30 19:48                       ` Valdis.Kletnieks at vt.edu
2014-07-30 20:45                         ` Nick Krause
2014-07-31 23:36                           ` Arlie Stephens
2014-07-31 23:41                             ` Henry Hallam
2014-08-01  1:47                               ` Nick Krause
  -- strict thread matches above, loose matches on Subject: below --
2007-02-28  3:05 Work Rick.Glenn

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=alpine.LFD.2.11.1407250814270.6376@localhost \
    --to=rpjday@crashcourse.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.