public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan-Simon Möller" <dl9pf@gmx.de>
To: Rob Landley <rob@landley.net>
Cc: Pavel Machek <pavel@suse.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	mtk.manpages@gmail.com, rdunlap@xenotime.net,
	linux-doc@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Trivial patch monkey <trivial@kernel.org>
Subject: Re: Document hadling of bad memory
Date: Fri, 28 Nov 2008 10:47:57 +0100	[thread overview]
Message-ID: <200811281047.57882.dl9pf@gmx.de> (raw)
In-Reply-To: <200811280300.26969.rob@landley.net>

Am Freitag 28 November 2008 10:00:26 schrieb Rob Landley:
> 
> So the patch isn't worth merging, but documentation about the out-of-tree 
> patch is worth merging?
Good point.

IIRC we tried merging the patch, but without luck at that time. It was said, that there's another method
(with an even <irony>better</irony> syntax) which could also handle this case and there should be better 
some hacking to get the syntax parsed to use the functions of this already in-kernel method.
I don't know the status of this (guess: none). 
What I know: badmem worked here really good. (But meantime I bought new ram.)

Best regards,
Jan-Simon

  reply	other threads:[~2008-11-28  9:48 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 [this message]
2008-11-28 12:18   ` Pavel Machek
2008-11-29  5:28     ` Rob Landley
2008-11-29  6:50   ` Andrew Morton
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=200811281047.57882.dl9pf@gmx.de \
    --to=dl9pf@gmx.de \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox