From: Francois Romieu <romieu@fr.zoreil.com>
To: bastardu@excite.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: One error . i really dont know what it is
Date: Sat, 28 Feb 2004 22:08:02 +0100 [thread overview]
Message-ID: <20040228220802.A28731@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20040228205305.3CF333D01@xprdmailfe4.nwk.excite.com>; from bastardu@excite.com on Sat, Feb 28, 2004 at 03:53:05PM -0500
bastardu@excite.com <bastardu@excite.com> :
[...]
> This is what i copyed from the screen i dont know if is going to help or
> i did something wrong. the kernel is 2.6.0 and that is all i know about it.
1 - It misses a few lines. :o(
2 - Upgrade to a more recent kernel
3 - 'locate REPORTING-BUGS' on your computer or google on
"REPORTING-BUGS linux kernel"
Thank you.
--
Ueimor
prev parent reply other threads:[~2004-02-28 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 20:53 bastardu
2004-02-28 21:08 ` Francois Romieu [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=20040228220802.A28731@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=bastardu@excite.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
all inboxes | Powered by JetHome®