Re: Giving developers clue how many testers verified certain kernel version

From: Adrian Bunk (bunk_at_stusta.de)
Date: 07/23/05

  • Next message: Karim Yaghmour: "Re: Merging relayfs?"
    Date:	Sat, 23 Jul 2005 01:22:23 +0200
    To: Alejandro Bonilla <abonilla@linuxwireless.org>
    
    

    On Thu, Jul 21, 2005 at 09:40:43PM -0500, Alejandro Bonilla wrote:
    >...
    > How does one check if hotplug is working better than before? How do
    > I test the fact that a performance issue seen in the driver is now fixed
    > for me or most of users? How do I get back to a bugzilla and tell that
    > there is a bug somewhere when one can't really know if that is the way
    > it works but is simply ugly, or if there is really a bug?
    >
    > My point is that a user like me, can't really get back to this
    > mailing list and say "hey, since 2.6.13-rc1, my PCI bus is having an
    > additional 1ms of latency" We don't really have a process to follow and
    > then be able to say "ahha, so this is different" and then report the
    > problem, even if we can't fix it because of our C and kernel skills.
    >
    > How do we know that something is OK or wrong? just by the fact that
    > it works or not, it doesn't mean like is OK.
    >
    > There has to be a process for any user to be able to verify and study a
    > problem. We don't have that yet.

    If the user doesn't notice the difference then there's no problem for
    him.

    If there's a problem the user notices, then the process is to send an
    email to linux-kernel and/or open a bug in the kernel Bugzilla and
    follow the "please send the output of foo" and "please test patch bar"
    instructions.

    What comes nearest to what you are talking about is that you run LTP
    and/or various benchmarks against every -git and every -mm kernel and
    report regressions. But this is sinply a task someone could do (and I
    don't know how much of it is already done e.g. at OSDL), and not
    something every user could contribute to.

    > .Alejandro

    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
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Karim Yaghmour: "Re: Merging relayfs?"

    Relevant Pages

    • Re: Bloat report 2.6.3 -> 2.6.4
      ... For the average computer you can buy at your supermarket today it isn't ... People who need to care about the size of the kernel use hand-tuned ... There had been need of rain for many days. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: ANNOUNCE: CE Linux Forum - Specification V1.0 draft
      ... Kernel SHALL be configuralble with compiler size options, ... "specification" didn't send a patch - the trivial patch was sent by ... There had been need of rain for many days. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: My thoughts on the "new development model"
      ... this was simple one more bug... ... IMHO Andrew+Linus should open a short-living 2.7 tree soon and Andrew ... There had been need of rain for many days. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Possible shared mapping bug in 2.4.23 (at least MIPS/Sparc)
      ... > Don't blame the kernel - the kernel is only doing what the user asked it ... Surely it's better to fail the mmapon other archs ... It's a bug either way ... ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Clock 3x too fast on AMD64 laptop [WAS Re: Various issues after rebooting]
      ... that bug report, is that disabling ACPI and/or APIC makes no difference. ... using a 64bit kernel and a 32bit kernel. ... At first, I thought the issue might be related to the nforce3, but the ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)