From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: testing a kernel - how can i help?
Date: Fri, 9 Sep 2005 23:53:53 +0200 [thread overview]
Message-ID: <6bffcb0e0509091453117d9978@mail.gmail.com> (raw)
In-Reply-To: <20050909204313.GA26469@vanheusden.com>
Hi,
On 09/09/05, Folkert van Heusden <folkert@vanheusden.com> wrote:
> Running klive on a sparc.
> Now I wonder: what should/can I run to help by testing a kernel? The sun
> is dedicated for the testing so everything is possible.
>
>
> Folkert van Heusden
>
You have at least 2 ways:
1 - test less bleeding edge -git and -rc, but it's hard, every day job :).
2 - test -mm - front line.
Regression tests? You can test every plugsched release or other useful thing.
Regards,
Michal Piotrowski
ps. My klive host: 6ce68650da42a5188df54b6989e153e0
ps.2 Sorry for my horrible English
prev parent reply other threads:[~2005-09-09 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 20:43 testing a kernel - how can i help? Folkert van Heusden
2005-09-09 21:53 ` Michal Piotrowski [this message]
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=6bffcb0e0509091453117d9978@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.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