public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda.linux@googlemail.com>
To: "Uwe Bugla" <uwe.bugla@gmx.de>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
Date: Sun, 27 May 2007 22:02:04 +0200	[thread overview]
Message-ID: <200705272202.04764.vda.linux@googlemail.com> (raw)
In-Reply-To: <20070524195616.234280@gmx.net>

On Thursday 24 May 2007 21:56, Uwe Bugla wrote:
> Please note:
> 
> 1. IRQ 255 looks very idiotic, doesn't it? It does not exist at all, does it?
> 
> Questions:
> 
> 1. What is the technical need / progress of module ssb please?
> 
> 2. If Andrew Morton's guidelines clearly say: "Do test your patches on three different machines" and this guideline seems to be strictly ignored by some sparetime hackers:
> 
> What is the master plan then to avoid the fact that such a crap is being sent in to Andrew?
> 
> Yours sincerely
> 
> Uwe
> 
> P. S.: There is an important saying going like this:
> 
> Too many cooks do mess up the pap.
> 
> Regarding the patch in mm-tree I can see SIX (!) Copyright owners.
> The last one of them (i. e. the one of 2007) obviuosly does not seem to understand what he is doing (see that nonsense interrupt please, just incredible!) :(
> 
> In so far I would deeply appreciate Andrew Morton to throw that b44.c patch into the trashbox as soon as possible :)

Uwe, you are an arrogant idiot and I think it's best
for everybody to just ignore all your mails, regardless
of their technical merits.

Even if your mail reports a real bug, added shitload of insults
to developers far outweights any possible useful info.

Developers can save a lot of time and nerver by just waiting for
someone else to hit the same bug, if it exists, and then debug it
as usual.
--
vda

  parent reply	other threads:[~2007-05-27 20:02 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 19:56 BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400) Uwe Bugla
2007-05-24 20:06 ` Andrew Morton
2007-05-24 21:16   ` Uwe Bugla
2007-05-25 13:16     ` Michael Buesch
2007-05-25 13:12   ` Michael Buesch
2007-05-25 13:20     ` Michael Buesch
2007-05-25 13:59     ` Uwe Bugla
2007-05-25 14:52       ` Michael Buesch
2007-05-25 15:59         ` Uwe Bugla
2007-05-25 16:23           ` Michael Buesch
2007-05-25 18:48           ` Maximilian Engelhardt
2007-05-25 19:40             ` Uwe Bugla
2007-05-26  5:00               ` Michael Buesch
2007-05-26  9:39                 ` Maximilian Engelhardt
2007-05-26 10:40                 ` Uwe Bugla
2007-05-26 15:36                   ` Michael Buesch
2007-05-26 15:52                     ` Uwe Bugla
2007-05-26 15:50                   ` Michael Buesch
2007-05-26 16:13                     ` Andrew Morton
2007-05-26 16:20                       ` Uwe Bugla
2007-05-26 16:46                         ` Francois Romieu
2007-05-26 16:21                       ` Michael Buesch
2007-05-26 16:26                         ` Uwe Bugla
2007-05-26 16:40                           ` Michael Buesch
2007-05-26 17:04                             ` Uwe Bugla
2007-05-26 17:18                               ` Michael Buesch
2007-05-26 17:24                                 ` Uwe Bugla
2007-05-26 18:03                                   ` Michael Buesch
2007-05-26 18:19                                     ` Andrew Morton
2007-05-26 19:38                                       ` Uwe Bugla
2007-05-26 19:57                                         ` Larry Finger
2007-05-26 20:22                                           ` Francois Romieu
2007-05-26 20:33                                           ` Uwe Bugla
2007-05-26 21:00                                             ` Michael Buesch
2007-05-26 18:41                                 ` Benoit Boissinot
2007-05-26 18:46                                   ` Michael Buesch
2007-05-26 18:58                                   ` Uwe Bugla
2007-05-26 19:14                                     ` Michael Buesch
2007-05-26 19:19                                     ` Michael Buesch
2007-05-26 19:39                                       ` Uwe Bugla
2007-05-26 19:49                                         ` Michael Buesch
2007-05-26 21:32                                           ` Uwe Bugla
2007-05-26 21:52                                             ` Dan Williams
2007-05-26 22:16                                               ` Uwe Bugla
2007-05-26 21:58                                             ` Michael Buesch
2007-05-26 19:04                       ` Michael Buesch
2007-05-28 12:12                       ` Michael Buesch
2007-05-26 16:14                     ` Uwe Bugla
2007-05-26 22:42                   ` David Miller
2007-05-25 16:56         ` Andrew Morton
2007-05-25 18:42           ` Uwe Bugla
2007-05-27 20:02 ` Denis Vlasenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-27 10:46 Uwe Bugla
2007-05-27 13:41 ` Kyle Moffett

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=200705272202.04764.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uwe.bugla@gmx.de \
    /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