From: Paul Mundt <lethal@linux-sh.org>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Steven J. Hill" <sjhill@realitydiluted.com>,
mips <linux-mips@linux-mips.org>
Subject: Re: [uClinux-dev] Re: Network problem in mips
Date: Fri, 12 Dec 2003 10:19:14 -0500 [thread overview]
Message-ID: <20031212151914.GA21619@linux-sh.org> (raw)
In-Reply-To: <20031211233058.GB20373@linux-mips.org>
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
On Fri, Dec 12, 2003 at 12:30:58AM +0100, Ralf Baechle wrote:
> > Seems a little out of order. Not everyone immediately understands you
> > need the ksyms to interpret a trace
>
> Guess that should be mentioned in the FAQ - anybody got a pointer to a
> little how to for writing useful bug reports?
>
What's wrong with the top-level REPORTING-BUGS? This specifically mentions
the need for oops tracing with pointers to relevant documentation prior to
posting the report.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-12 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 14:57 Network problem in mips durai
2003-12-11 15:25 ` Steven J. Hill
2003-12-11 23:07 ` Alan Cox
2003-12-11 23:30 ` Ralf Baechle
2003-12-11 23:46 ` Maciej W. Rozycki
2003-12-13 1:10 ` Ralf Baechle
2003-12-12 15:19 ` Paul Mundt [this message]
2003-12-12 19:25 ` Alan Cox
2003-12-12 7:44 ` durai
2003-12-12 17:42 ` Steven J. Hill
2003-12-13 2:48 ` Ralf Baechle
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=20031212151914.GA21619@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@linux-mips.org \
--cc=sjhill@realitydiluted.com \
--cc=uclinux-dev@uclinux.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