From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to test my patches before submitting them to LKML?
Date: Fri, 7 Feb 2014 14:05:52 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1402071404090.3494@localhost> (raw)
In-Reply-To: <36523.1391797811@turing-police.cc.vt.edu>
On Fri, 7 Feb 2014, Valdis.Kletnieks at vt.edu wrote:
> On Fri, 07 Feb 2014 18:30:46 +0100, Matthias Beyer said:
>
> > So you would say, I should start patching non-hardware driver code,
> > FS for example, to get my feet wet with the kernel?
>
> You might want to take a step back, be a bit more meta, and ask
> yourself why, exactly, you want to do kernel hacking at all. If
> there isn't an obvious part of the kernel that interests you, maybe
> kernel hacking isn't where you should be.
i get asked the same thing on a regular basis, and i've learned to
respond, "have you already downloaded the source, pawed through it,
configured it, compiled it and rebooted it? if not, that's where you
start." no point talking about *hacking* the kernel until you've
worked through the basics of just building and booting one.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-02-07 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 15:31 How to test my patches before submitting them to LKML? Matthias Beyer
2014-02-07 16:10 ` Valdis.Kletnieks at vt.edu
2014-02-07 17:30 ` Matthias Beyer
2014-02-07 18:30 ` Valdis.Kletnieks at vt.edu
2014-02-07 19:05 ` Robert P. J. Day [this message]
2014-02-07 20:51 ` Arlie Stephens
2014-02-07 23:46 ` Valdis.Kletnieks at vt.edu
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.1402071404090.3494@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 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).