From: Andrew Morton <akpm@zip.com.au>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Antti Salmela <asalmela@iki.fi>, linux-kernel@vger.kernel.org
Subject: Re: [OOPS] 2.4.17, SMP, AMD, devfs, highmem.
Date: Wed, 23 Jan 2002 11:33:32 -0800 [thread overview]
Message-ID: <3C4F100C.5F817D73@zip.com.au> (raw)
In-Reply-To: <20020123152406.A4992@wasala.fi>, <20020123152406.A4992@wasala.fi> <200201231749.g0NHn1h31634@vindaloo.ras.ucalgary.ca>
Richard Gooch wrote:
>
> Antti Salmela writes:
> > Kernel compiled with gcc version 2.95.4 (Debian prerelease).
> >
> > If any additional information is required, please ask.
>
> If you had searched the list archives, you would have seen that this
> bug has already been fixed. Even if you're too lazy to do that, you
> should at least apply the latest pre-patch (2.4.18-pre6 as I write
> this) and see if the problem goes away. That's standard procedure:
> always try to reproduce an Oops using the latest kernel. 2.4.17 is
> over a month old: a lot has happened since then.
>
Richard, that's just completely over the top. Antti is quite
justified in reporting a problem against the stable kernel,
particularly when it has a version number as late as 2.4.17.
We want *more* bug reports, not less. And if some of them
are dupes, then we should just roll with it and be polite.
It's not reasonable to send everyone away to trawl the archives,
read the prerelease changelogs, etc. That's just shooting
ourselves in the feet.
-
prev parent reply other threads:[~2002-01-23 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 13:24 [OOPS] 2.4.17, SMP, AMD, devfs, highmem Antti Salmela
2002-01-23 17:49 ` Richard Gooch
2002-01-23 19:33 ` Andrew Morton [this message]
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=3C4F100C.5F817D73@zip.com.au \
--to=akpm@zip.com.au \
--cc=asalmela@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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