From mboxrd@z Thu Jan 1 00:00:00 1970 From: rpjday@crashcourse.ca (Robert P. J. Day) Date: Fri, 7 Feb 2014 14:05:52 -0500 (EST) Subject: How to test my patches before submitting them to LKML? In-Reply-To: <36523.1391797811@turing-police.cc.vt.edu> References: <20140207153104.GW27070@fu.3gs> <22342.1391789459@turing-police.cc.vt.edu> <20140207173046.GX27070@fu.3gs> <36523.1391797811@turing-police.cc.vt.edu> Message-ID: To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org 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 ========================================================================