linux-kernel - Re: Document hadling of bad memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Nov 2008 22:50:32 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Rob Landley <rob@...dley.net>
Cc:	Pavel Machek <pavel@...e.cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	mtk.manpages@...il.com, dl9pf@....de, rdunlap@...otime.net,
	linux-doc@...r.kernel.org,
	Trivial patch monkey <trivial@...nel.org>
Subject: Re: Document hadling of bad memory

On Fri, 28 Nov 2008 03:00:26 -0600 Rob Landley <rob@...dley.net> wrote:

> On Wednesday 26 November 2008 10:15:21 Pavel Machek wrote:
> > Document how to deal with bad memory reported with memtest.
> ...
> > +BadRAM
> > +######
> > +BadRAM is the actively developed and available as kernel-patch
> > +here:  http://rick.vanrein.org/linux/badram/
> 
> So the patch isn't worth merging, but documentation about the out-of-tree 
> patch is worth merging?
> 
> I'm not objecting, I'm just confused about to what the merge criteria are...
> 

mm..  If someone finds it useful (and I assume that at least one person
would have found it useful, hence the effort to write the patch) then
why not?

(And yeah, yeah, someone might find a .gif of a parrot useful too.  Go
do some work.)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/