From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to fast master kernel
Date: Tue, 10 May 2016 18:24:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1605101824030.7216@localhost.localdomain> (raw)
In-Reply-To: <52618.1462917526@turing-police.cc.vt.edu>
On Tue, 10 May 2016, Valdis.Kletnieks at vt.edu wrote:
> On Tue, 10 May 2016 16:58:26 -0400, "Robert P. J. Day" said:
>
> > not sure who it was (maybe even valdis) who once said, "Saying you
> > want to get into kernel programming but have no idea where to start so
> > can someone give you suggestions is like saying you want to write a
> > book but don't know what to write about so can someone give you any
> > ideas."
>
> Yeah, that was me...
>
> I'm also the one who said that we're approaching the point where the
> number of people who are actually qualified to do serious hacking on
> the kernel innards (like the scheduler, vfs, etc, not just a driver)
> is on the same order of magnitude as the number of people qualified
> to be Formula-1 race car mechanics....
all those F-1 race cars run linux, anyway, so ... no big deal.
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:[~2016-05-10 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 2:58 How to fast master kernel Aric
2016-05-10 8:32 ` Matthew Bobrowski
2016-05-10 15:00 ` Valdis.Kletnieks at vt.edu
2016-05-10 20:58 ` Robert P. J. Day
2016-05-10 21:58 ` Valdis.Kletnieks at vt.edu
2016-05-10 22:24 ` Robert P. J. Day [this message]
2016-05-11 5:07 Aric
[not found] <tencent_11C81A8B074E9D774D6DCA28@qq.com>
2016-05-11 17:32 ` 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.20.1605101824030.7216@localhost.localdomain \
--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.