Re: How to improve the quality of the kernel?

[Martin Bligh <mbligh@mbligh.org>]

> > > 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.

if it's free text it'll be useless for search ... I suppose we could
do drop-downs for architecture at least? Not sure much beyond that
would work ... *possibly* the common drivers, but I don't think
we'd get enough coverage for it to be of use.

M.
-
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/