From: kennethadammiller@gmail.com (Kenneth Adam Miller)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Safety in Kernel Development
Date: Wed, 19 Aug 2015 09:20:41 -0400 [thread overview]
Message-ID: <CAK7rcp86=3Fm_yCN-qzC5EQwOMy7edN2P+nzFHHeUXqn8g2v1g@mail.gmail.com> (raw)
In-Reply-To: <55D42ED4.5060005@mrbrklyn.com>
Ok, agreed. I hadn't known that much - I apologize for getting this to the
wrong list. I've not at all proposed any kernel overhaul effort, only how
to affect my own code. :)
Thank you to all mentors who gave advice. :)
On Wed, Aug 19, 2015 at 3:23 AM, Ruben Safir <ruben@mrbrklyn.com> wrote:
> On 08/18/2015 08:30 PM, Kenneth Adam Miller wrote:
> > | "this is not a rational approach"
> >
> > I'm very strongly confident the approach of achieving stronger guarantees
>
>
> Off topic
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150819/04b03484/attachment.html
prev parent reply other threads:[~2015-08-19 13:20 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
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 [this message]
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='CAK7rcp86=3Fm_yCN-qzC5EQwOMy7edN2P+nzFHHeUXqn8g2v1g@mail.gmail.com' \
--to=kennethadammiller@gmail.com \
--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).