Re: How to improve the quality of the kernel?

On 6/18/07, Fortier,Vincent [Montreal] <Vincent.Fortier1@xxxxxxxx> wrote:
> -----Message d'origine-----
> De : linux-kernel-owner@xxxxxxxxxxxxxxx
> [mailto:linux-kernel-owner@xxxxxxxxxxxxxxx] De la part de
> Andrew Morton
>
> On Mon, 18 Jun 2007 01:15:15 +0200 Stefan Richter
> <stefanr@xxxxxxxxxxxxxxxxx> wrote:
>
> > Tested-by
>
> Tested-by would be good too. Because over time, we will
> generate a list of people who own the relevant hardware and
> who are prepared to test changes.

Why not include a user-space tool that, when invoked, if you agree to
send personnal info, sends your hardware vs driver info to a web
database + your email address (maybie even you .config, etc..) ... In
case of help for testing new patches/finding a bug/etc.. your email
could be used by maintainers to ask for help...

> So if you make changes to random-driver.c you can do `git-log
> random-driver.c|grep Tested-by" to find people who can test
> your changes for you.

You would'nt even need to search in GIT. Maybie even when ever a
patchset is being proposed a mail could be sent to appropriate
hardware/or feature pseudo-auto-generated mailing-list?

On lkml I mostly try to follow patches/bugs associated with hardware I
use. Why not try to automate the process and get more testers in?


I think this is an excellent point. One data point could be a field in
bugzilla to input the hardware information. Simple query can select
common hardware and platform. So far it's not working when hardware is
just mentioned in the text part.

--Natalie

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

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

Relevant Pages

  • Re: TCP/IP send, sendfile, RAW
    ... Is this bad hardware or is the cost of sendto that high. ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: Question on HDLC and raw access to T1/E1 serial streams.
    ... hardware though aimed at voice work lets software get in at an extremely ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: Clock has stopped (time/date looping over 5 seconds), things are broken - what to check to d
    ... What hardware are you running on? ... and a number of other things fail to work. ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: [2.6 patch] make INPUT a bool
    ... this is irrelevant since CONFIG_INPUT alone does not init any hardware. ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: [PATCH] intel-iommu: Fix array overflow
    ... hardware may be able to generate more types of faults, ... a BUG here. ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)