kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Safety in Kernel Development
Date: Tue, 18 Aug 2015 09:40:48 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1508180940100.13331@localhost> (raw)
In-Reply-To: <CAK7rcp93Jvy73RxDLKnMgMBoiYz75P5pii6v=nXhZhWEArrRmw@mail.gmail.com>

On Tue, 18 Aug 2015, Kenneth Adam Miller wrote:

> Ok- so I know that C is the defacto standard for kernel
> development...

  and that's probably where you should have stopped typing. :-)

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:[~2015-08-18 13:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 13:25 Safety in Kernel Development Kenneth Adam Miller
2015-08-18 13:40 ` Robert P. J. Day [this message]
2015-08-18 13:45   ` Kenneth Adam Miller
2015-08-18 13:58     ` 慕冬亮
2015-08-18 15:25       ` Greg KH
2015-08-18 15:46       ` Valdis.Kletnieks at vt.edu
2015-08-18 14:01     ` leo kirotawa
2015-08-18 14:03       ` Kenneth Adam Miller
2015-08-18 22:22         ` Ruben Safir
2015-08-18 15:01       ` Victor Rodriguez
2015-08-18 15:03         ` Kenneth Adam Miller
2015-08-18 13:52 ` Victor Rodriguez
2015-08-18 14:01   ` Kenneth Adam Miller
2015-08-18 22:27 ` Ruben Safir
2015-08-19  0:30   ` Kenneth Adam Miller
2015-08-19  7:22     ` Ruben Safir
2015-08-19  7:23     ` Ruben Safir
2015-08-19 13:20       ` Kenneth Adam Miller

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.1508180940100.13331@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).