From: Jody Bruchon <jody@jodybruchon.com>
To: linux-8086@vger.kernel.org
Subject: [RFC] Possible ELKS bug fixes in "nanox" project
Date: Sat, 11 Feb 2012 13:56:58 -0500 [thread overview]
Message-ID: <4F36B9FA.4020303@jodybruchon.com> (raw)
This project is based on ELKS:
http://code.google.com/p/nanox/source/browse/#svn%2Ftrunk
There are some bug fixes and feature improvements within that I'm
interested in adding to the ELKS code base, but I'd like for others on
the list to review them first. Some of the fixes are already applied in
Git, but others are not, and it also appears that the individual who
maintained this project wrote some direct console code which could be
helpful...assuming it works and doesn't break other things.
Can someone test some of these changes? Preferably on real hardware if
possible.
Thanks in advance.
Jody Bruchon
reply other threads:[~2012-02-11 18:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F36B9FA.4020303@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@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 read-only IMAP folder(s) and NNTP newsgroup(s).