From: Jan Kiszka <jan.kiszka@domain.hid>
To: nishit sharma <sharmafrequent@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] kernel crashes
Date: Mon, 25 Jun 2007 12:13:49 +0200 [thread overview]
Message-ID: <467F955D.4040503@domain.hid> (raw)
In-Reply-To: <3480a2190706250254q9daf8e4je6319dce206a11a2@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
nishit sharma wrote:
> Hi,
> why kernel crashes when driver module is inserted and its user application
> is run in background and ls command is entered.
> But the same code is stable for another architecture.
I'm afraid I'll have to state this more explicitly:
Please stop flooding the list with useless bug reports!
We will be all ears once your MIPS port has been released to the
community. But until then it's pointless (and even potentially
misleading for uninformed observers) to report bugs that are
_most_likely_ only in your _private_ code.
Thanks,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2007-06-25 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 9:54 [Xenomai-help] kernel crashes nishit sharma
2007-06-25 10:10 ` Dmitry Adamushko
2007-06-25 10:13 ` Jan Kiszka [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=467F955D.4040503@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=sharmafrequent@domain.hid \
--cc=xenomai@xenomai.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.