From: "Mike Frysinger" <vapier.adi@gmail.com>
To: monstr@seznam.cz
Cc: "Linux Kernel list" <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: LTP for no MMU systems
Date: Tue, 6 May 2008 10:49:04 -0400 [thread overview]
Message-ID: <8bd0f97a0805060749j28cb6fe6wfbdf0d3948d2f417@mail.gmail.com> (raw)
In-Reply-To: <48206ECF.9090005@seznam.cz>
On Tue, May 6, 2008 at 10:44 AM, Michal Simek <monstr@seznam.cz> wrote:
> I tested Microblaze MMU kernel for finding where could be problem. I have no
> problem with compilation. Microblaze MMU test result is on
> http://www.monstr.eu/wiki/doku.php?id=kernel:testing.
>
> I would like to test no MMU kernel too. Does anyone use it for no MMU kernel?
> (Blackfin, m68k and others)
yes, we run many of the tests under testcases/kernel/ on Blackfin
-mike
next prev parent reply other threads:[~2008-05-06 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 14:44 LTP for no MMU systems Michal Simek
2008-05-06 14:49 ` Mike Frysinger [this message]
2008-05-06 15:26 ` Michal Simek
2008-05-06 15:37 ` Mike Frysinger
2008-05-07 6:31 ` Michal Simek
2008-05-07 6:56 ` Mike Frysinger
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=8bd0f97a0805060749j28cb6fe6wfbdf0d3948d2f417@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@seznam.cz \
/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