From: Andrew Morton <akpm@linux-foundation.org>
To: Rob Landley <rob@landley.net>
Cc: Pavel Machek <pavel@suse.cz>,
kernel list <linux-kernel@vger.kernel.org>,
mtk.manpages@gmail.com, dl9pf@gmx.de, rdunlap@xenotime.net,
linux-doc@vger.kernel.org,
Trivial patch monkey <trivial@kernel.org>
Subject: Re: Document hadling of bad memory
Date: Fri, 28 Nov 2008 22:50:32 -0800 [thread overview]
Message-ID: <20081128225032.0ddeb1b8.akpm@linux-foundation.org> (raw)
In-Reply-To: <200811280300.26969.rob@landley.net>
On Fri, 28 Nov 2008 03:00:26 -0600 Rob Landley <rob@landley.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.)
next prev parent reply other threads:[~2008-11-29 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 16:15 Document hadling of bad memory Pavel Machek
2008-11-26 16:25 ` Jan-Simon Möller
2008-11-27 0:42 ` Jiri Kosina
2008-11-28 9:00 ` Rob Landley
2008-11-28 9:47 ` Jan-Simon Möller
2008-11-28 12:18 ` Pavel Machek
2008-11-29 5:28 ` Rob Landley
2008-11-29 6:50 ` Andrew Morton [this message]
2008-12-01 18:56 ` Randy Dunlap
2008-12-09 12:31 ` Pavel Machek
2008-12-09 21:40 ` Rob Landley
2008-12-09 23:11 ` Pavel Machek
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=20081128225032.0ddeb1b8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dl9pf@gmx.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=pavel@suse.cz \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.net \
--cc=trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.