From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
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>
Subject: Re: Network problem in mips
Date: Sat, 13 Dec 2003 02:10:17 +0100 [thread overview]
Message-ID: <20031213011017.GB22448@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0312120037480.23228@jurand.ds.pg.gda.pl>
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
next prev parent reply other threads:[~2003-12-13 1:10 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 [this message]
2003-12-12 15:19 ` [uClinux-dev] " Paul Mundt
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=20031213011017.GB22448@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=durai@isofttech.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--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