From: Andi Kleen <andi-Vw/NltI1exuRpAAqCnN02g@public.gmane.org>
To: devzero-S0/GAf8tV78@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: suse slab testing module "crasher"
Date: Sun, 15 Jun 2008 20:37:40 +0200 [thread overview]
Message-ID: <48556174.9090708@firstfloor.org> (raw)
In-Reply-To: <317948575-S0/GAf8tV78@public.gmane.org>
>
> so, if it`s useful, who is reponsible for pushing it upstream ?
Nobody is. That is why it isn't. Feel free to do the work.
It would need some cleanup before submission. e.g. the ooops/panic etc. options
are fairly useless and should be removed and there needs to be more documentation.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: devzero@web.de
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
kernel-testers@vger.kernel.org
Subject: Re: suse slab testing module "crasher"
Date: Sun, 15 Jun 2008 20:37:40 +0200 [thread overview]
Message-ID: <48556174.9090708@firstfloor.org> (raw)
In-Reply-To: <317948575@web.de>
>
> so, if it`s useful, who is reponsible for pushing it upstream ?
Nobody is. That is why it isn't. Feel free to do the work.
It would need some cleanup before submission. e.g. the ooops/panic etc. options
are fairly useless and should be removed and there needs to be more documentation.
-Andi
next prev parent reply other threads:[~2008-06-15 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 18:31 suse slab testing module "crasher" devzero-S0/GAf8tV78
2008-06-15 18:31 ` devzero
[not found] ` <317948575-S0/GAf8tV78@public.gmane.org>
2008-06-15 18:37 ` Andi Kleen [this message]
2008-06-15 18:37 ` Andi Kleen
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=48556174.9090708@firstfloor.org \
--to=andi-vw/nlti1exurpaaqcnn02g@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=devzero-S0/GAf8tV78@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.