linux-mips
[Top] [All Lists]

Re: [uClinux-dev] Re: Network problem in mips

To: uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: [uClinux-dev] Re: Network problem in mips
From: Paul Mundt <lethal@linux-sh.org>
Date: Fri, 12 Dec 2003 10:19:14 -0500
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, "Steven J. Hill" <sjhill@realitydiluted.com>, mips <linux-mips@linux-mips.org>
In-reply-to: <20031211233058.GB20373@linux-mips.org>
Mail-followup-to: Paul Mundt <lethal@linux-sh.org>, uClinux development list <uclinux-dev@uclinux.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>, "Steven J. Hill" <sjhill@realitydiluted.com>, mips <linux-mips@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <008f01c3bff7$252e3b40$0a05a8c0@DURAI> <3FD88C4D.6010700@realitydiluted.com> <1071184052.19738.12.camel@dhcp23.swansea.linux.org.uk> <20031211233058.GB20373@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
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: pgpBxQewbaKsj.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>