linux-mips
[Top] [All Lists]

Re: Network problem in mips

To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: Network problem in mips
From: Ralf Baechle <ralf@linux-mips.org>
Date: Sat, 13 Dec 2003 02:10:17 +0100
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, "Steven J. Hill" <sjhill@realitydiluted.com>, durai <durai@isofttech.com>, uclinux-dev <uclinux-dev@uclinux.org>, mips <linux-mips@linux-mips.org>
In-reply-to: <Pine.LNX.4.55.0312120037480.23228@jurand.ds.pg.gda.pl>
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> <Pine.LNX.4.55.0312120037480.23228@jurand.ds.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Fri, Dec 12, 2003 at 12:46:23AM +0100, Maciej W. Rozycki 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?
> 
>  Well, REPORTING-BUGS in the Linux source seems pretty good for a start.  
> README provides a few hints as well, although with a little bias towards
> i386.

Indeed.  So close I already forgot about this file's existence ...

I added a short section about bug reporting to the FAQ.  Less than perfect
but at least it's a start.

  Ralf

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