public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Keith Owens <kaos@ocs.com.au>
Cc: spyro@armlinux.org, linux-kernel@vger.kernel.org
Subject: Re: usb-uhci *BUG*
Date: Sun, 14 Apr 2002 10:26:32 +0100	[thread overview]
Message-ID: <20020414102632.A30379@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020414004022.6450f038.spyro@armlinux.org> <32607.1018743108@ocs3.intra.ocs.com.au>

On Sun, Apr 14, 2002 at 10:11:48AM +1000, Keith Owens wrote:
> Any particular reason for not using ksymoops?  If it does not work on
> arm, I can get rid of all the arm code ;).

It does work on ARM.  I use it, and we've had a few posts using it.
However, since it took several _months_ for the ksymoops version with
the fixed regexps for ARM to come out, I don't really think you're
justified in the above comments.

However, it's just that most people don't bother to think about reading
any documentation (like REPORTING-BUGS) and think that just posting
random bits is sufficient.  It's difficult enough to get these people to
post basic things like kernel versions and so forth.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-04-14  9:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 23:40 usb-uhci *BUG* Ian Molton
2002-04-13 23:44 ` Ian Molton
2002-04-14  0:11 ` Keith Owens
2002-04-14  9:26   ` Russell King [this message]
2002-04-14  9:49     ` Keith Owens
2002-04-14 15:07 ` Greg KH
2002-04-14 17:32   ` Ian Molton
2002-04-14 16:43     ` Greg KH
2002-04-14 18:25       ` Ian Molton
2002-04-14 17:52         ` Greg KH
2002-04-14 19:01       ` Pierre Rousselet
2002-04-14 19:21         ` Ian Molton
2002-04-14 19:32           ` Pierre Rousselet
2002-04-14 20:43             ` Ian Molton

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=20020414102632.A30379@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spyro@armlinux.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