public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Martin MOKREJ <mmokrejs@ribosome.natur.cuni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Giving developers clue how many testers verified certain kernel version
Date: Sun, 24 Jul 2005 20:54:19 +0200	[thread overview]
Message-ID: <20050724185419.GV3160@stusta.de> (raw)
In-Reply-To: <42E3E1BC.2050509@ribosome.natur.cuni.cz>

On Sun, Jul 24, 2005 at 08:45:16PM +0200, Martin MOKREJ? wrote:

> Hi Adrian,

Hi Martin,

>  well, the idea was to give you a clue how many people did NOT complain
> because it either worked or they did not realize/care. The goal
> was different. For example, I have 2 computers and both need current acpi
> patch to work fine. I went to bugzilla and found nobody has filed such bugs
> before - so I did and said it is already fixed in current acpi patch.
> But you'd never know that I tested that successfully. And I don't believe
> to get emails from lkml that I installed a patch and it did not break
> anything. I hope you get the idea now. ;)

in your ACPI example there is a bug/problem (ACPI needs updating).

And ACPI is a good example where even 1000 success reports wouldn't help 
because a slightly different hardware or BIOS version might make the 
difference.

Usually "no bug report" indicates that something is OK.
And if you are unsure whether an unusual setup or hardware is actually 
tested, it's usually the best to ask on linux-kernel whether someone 
could test it.

> Martin

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-07-24 18:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22  1:34 Giving developers clue how many testers verified certain kernel version Martin MOKREJŠ
2005-07-22  2:10 ` Mark Nipper
2005-07-22  2:38   ` Martin MOKREJŠ
2005-07-22  2:40     ` Alejandro Bonilla
2005-07-22 23:22       ` Adrian Bunk
2005-07-22 23:11 ` Adrian Bunk
2005-07-24 18:45   ` Martin MOKREJŠ
2005-07-24 18:54     ` Adrian Bunk [this message]
2005-07-24 19:10       ` Martin MOKREJŠ
  -- strict thread matches above, loose matches on Subject: below --
2005-07-23  0:44 Blaisorblade
2005-07-23  0:50 ` David Lang
2005-07-23  0:59   ` H. Peter Anvin
2005-07-23  1:07 ` Alejandro Bonilla
2005-07-23  3:09   ` Lee Revell
2005-07-23  2:15     ` Alejandro Bonilla
2005-07-23  3:21       ` Lee Revell
2005-07-23  2:34         ` Alejandro Bonilla
2005-07-23  3:31         ` Linus Torvalds
2005-07-23  2:40           ` Alejandro Bonilla
2005-07-23  3:34           ` Lee Revell
2005-07-23  9:05             ` Con Kolivas
2005-07-23 16:45               ` Lee Revell
2005-07-23  3:56       ` Adrian Bunk
2005-07-23  9:21 ` Jesper Krogh

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=20050724185419.GV3160@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    /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