public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: davem@redhat.com
Cc: linux-kernel@vger.kernel.org, tcallawa@redhat.com,
	colin@gibbs.dhs.org, sparclinux@vger.kernel.org,
	aurora-sparc-devel@linuxpower.org
Subject: Re: [aurora-sparc-devel] Re: 2.4 SRMMU bug revisited
Date: Mon, 27 May 2002 13:19:52 +0200	[thread overview]
Message-ID: <20020527111951.GA1302@louise.pinerecords.com> (raw)
In-Reply-To: <20020527092408.GD345@louise.pinerecords.com> <20020527.031732.95158135.davem@redhat.com> <20020527062044.GA6737@beth.pinerecords.com> <20020527.034039.120708891.davem@redhat.com>

>    > %99 of people with sparc32 problems are totally unwilling (or unable)
>    > to help fix the bugs themselves, they merely whine.  It gets a bit
>    > old after a while (which for me amount to roughly 7 years).
>    
>    Sure, I'm willing to try to write the fix if someone takes the time
>    to explain to me what's happening -- I'm quite fluent in C but know
>    nothing about the anatomy of the problem.
> 
> See the part where I mention "unable".


Whoa. Let me recapitulate:
	- first I provide feedback on patches.

	-> I'm told I'm not helping but merely whining.

	- then I offer to fix the problem myself given somebody explains
	what's going on in the code so that I at least know where to start
	and what to look for.

	-> I am told by DaveM to re-read a sentence by DaveM that seems
	to inform me that even if I'm willing to help, I'm likely not able
	to, anyway.

Hello!! How exactly is *this* helping then?


T.

  reply	other threads:[~2002-05-27 11:20 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       ` Tomas Szepe [this message]
2002-05-28 16:41         ` [aurora-sparc-devel] " Denis Vlasenko
2002-05-28 12:11           ` David S. Miller
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=20020527111951.GA1302@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=aurora-sparc-devel@linuxpower.org \
    --cc=colin@gibbs.dhs.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tcallawa@redhat.com \
    /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