From: "David S. Miller" <davem@redhat.com>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: szepe@pinerecords.com, linux-kernel@vger.kernel.org
Subject: Re: [aurora-sparc-devel] Re: 2.4 SRMMU bug revisited
Date: Tue, 28 May 2002 05:11:34 -0700 (PDT) [thread overview]
Message-ID: <20020528.051134.58832375.davem@redhat.com> (raw)
In-Reply-To: <200205281139.g4SBdSY22504@Port.imtp.ilyichevsk.odessa.ua>
From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Date: Tue, 28 May 2002 14:41:20 -0200
But he wants some of "%99 of people with sparc32 problems" to move
into "%1" category instead.
Thank you, that is exactly what I meant.
Look, if someone reports some bug once, that's ok. You report it
twice, I'll give you the benefit of the doubt that you're merely
reminding us. The third and further time, it's a whine. Everyone
here knows there are sun4m problems, and Tom in particular knows it is
a well known problem because I know he reads this list. Therefore Tom
was engaging in what I'd like to term a double-whine.
next prev parent reply other threads:[~2002-05-28 12:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 9:24 2.4 SRMMU bug revisited Tomas Szepe
2002-05-27 10:17 ` David S. Miller
2002-05-27 6:20 ` Tomas Szepe
2002-05-27 10:40 ` David S. Miller
2002-05-27 11:19 ` [aurora-sparc-devel] " Tomas Szepe
2002-05-28 16:41 ` Denis Vlasenko
2002-05-28 12:11 ` David S. Miller [this message]
2002-05-27 18:46 ` Colin Gibbs
2002-05-27 19:34 ` Colin Gibbs
2002-05-28 1:12 ` Tomas Szepe
2002-05-27 21:30 ` Tomas Szepe
2002-05-28 3:41 ` David S. Miller
2002-05-28 5:40 ` Tomas Szepe
2002-05-28 8:39 ` David Woodhouse
2002-05-28 11:58 ` Alan Cox
2002-05-28 11:05 ` David S. Miller
2002-05-28 12:10 ` Ben Collins
2002-05-28 12:19 ` David S. Miller
2002-05-28 0:40 ` David S. Miller
2002-05-29 21:42 ` Tomas Szepe
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=20020528.051134.58832375.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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