From: Chris Jones <chrisjones@spin.net.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Integrating a new programming language into the kernel
Date: Mon, 14 May 2012 18:28:44 +1000 [thread overview]
Message-ID: <20120514182844.1b9c3614@linux-j2xc> (raw)
In-Reply-To: <20120514074149.GA12756@kroah.com>
Thanks, I will. It's all part of the hacking fun!
Cheers
Chris Jones
On Mon, 14 May 2012 00:41:49 -0700
Greg KH <greg@kroah.com> wrote:
> On Mon, May 14, 2012 at 01:57:31PM +1000, Chris Jones wrote:
> > I'm curious as to why you suggest "no"?
> >
> > And if it were to successfully eventuate and I were to do this, it
> > would only ever be a custom kernel. And that's why I'm curious as to
> > why you say to not do it.
>
> Try it and find out why he, and others, recommend not to do so :)
>
> Best of luck,
>
> greg k-h
next prev parent reply other threads:[~2012-05-14 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 2:00 Integrating a new programming language into the kernel Chris Jones
2012-05-14 0:43 ` H. Peter Anvin
2012-05-14 3:57 ` Chris Jones
2012-05-14 7:41 ` Greg KH
2012-05-14 8:28 ` Chris Jones [this message]
2012-05-14 7:46 ` richard -rw- weinberger
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=20120514182844.1b9c3614@linux-j2xc \
--to=chrisjones@spin.net.au \
--cc=linux-kernel@vger.kernel.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).