From: "Lee Revell" <rlrevell@joe-job.com>
To: "devzero@web.de" <devzero@web.de>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com, pavel@suse.cz
Subject: Re: [RFC] BadRAM still not ready for inclusion ? (was: Re: Free Linux Driver Development!)
Date: Tue, 6 Mar 2007 12:23:21 -0500 [thread overview]
Message-ID: <75b66ecd0703060923yc73b796w3aae193ed5f8d9ee@mail.gmail.com> (raw)
In-Reply-To: <1663310550@web.de>
On 3/4/07, devzero@web.de <devzero@web.de> wrote:
> It seems, that BadRAM is not being maintained very actively and the original author doesn`t seem to have the time pushing it into mainline, but i know it's actively being used by more then just a handful of people. Unfortunately there is no mailinglist to approve this and some "central point of communication" besides Rick van Rein doesn't seem to exist. There is a fork named BadMEM at http://sourceforge.net/projects/badmem, Memtest86 also supporting BadRAM and i have seen LOTs of discussion about BadRAM on the net. Most of that discussion was due to problems getting it run with Kernel XYZ.
>
> Basically, this feature is a matter of adding/modifying 200 lines of code, so iŽm even more wondering, why it exists for more than 7 years and nothing happening here.
Because most kernel developers don't have time to scour the net for
random kernel patches and pull them. If you have a useful patch you
want merged it's up to you to push it.
What's so hard about submitting a 200 line patch to LKML?
Lee
next prev parent reply other threads:[~2007-03-06 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 19:13 devzero
[not found] ` <f24d23310703041204r2e729cc4ke93a9cbb70ef2e85@mail.gmail.com>
2007-03-04 20:06 ` debian developer
2007-03-06 17:12 ` Bill Davidsen
2007-03-06 17:23 ` Lee Revell [this message]
2007-03-06 17:54 devzero
2007-03-07 9:03 ` Pavel Machek
2007-03-06 18:02 devzero
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=75b66ecd0703060923yc73b796w3aae193ed5f8d9ee@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=devzero@web.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®