linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: David Lang <dlang@digitalinsight.com>,
	Arnaud Patard <apatard@mandriva.com>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: automated test? (was Re: Linux 2.6.17.7)
Date: Wed, 26 Jul 2006 17:00:41 +0200	[thread overview]
Message-ID: <20060726150041.GG23701@stusta.de> (raw)
In-Reply-To: <200607261539.50492.adq_dvb@lidskialf.net>

On Wed, Jul 26, 2006 at 03:39:49PM +0100, Andrew de Quincey wrote:
> On Wednesday 26 July 2006 15:29, Adrian Bunk wrote:
>...
> > The real problem is:
> > How do we get some testing coverage of -stable kernels by users to catch
> > issues?
> > And compile errors are the least of my worries.
> 
> Yeah - I believe some people did test the DVB -stable patches, but obviously 
> without the budget-av driver compile option enabled, so it didn't compile 
> that code. DVB supports quite a few cards, so its easy to accidentally leave 
> off one of the options when doing a mass compile of all drivers.
> 
> The only thing I can think of would be to require -stable patch submitters to 
> supply a list of CONFIG options that must be on to enable compilation of the 
> new code so people know exactly how to enable it for testing... but obviously 
> since those would be manually specified, they can be wrong too. But at least 
> it would show they'd thought about it a bit....

This helps only with compilation errors, which are as I said the least 
of my worries.

But does the hardware driven by this driver work?
And if it does, is there a bug in the patch that causes the kernel to 
crash after some hours?

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:[~2006-07-26 15:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25  3:42 Linux 2.6.17.7 Greg KH
2006-07-25  3:43 ` Greg KH
2006-07-25  9:55 ` Arnaud Patard
2006-07-25 10:23   ` Andrew de Quincey
2006-07-25 16:47     ` automated test? (was Re: Linux 2.6.17.7) David Lang
2006-07-25 16:56       ` Arjan van de Ven
2006-07-25 17:07         ` Michael Krufky
2006-07-25 18:42           ` Jean Delvare
2006-07-25 19:26             ` Andrew de Quincey
2006-07-25 21:20         ` Matthias Andree
2006-07-25 21:28           ` David Lang
2006-07-25 20:10       ` Arnaud Patard
2006-07-26 13:02       ` Adrian Bunk
2006-07-26 14:10         ` Andrew de Quincey
2006-07-26 14:29           ` Adrian Bunk
2006-07-26 14:39             ` Andrew de Quincey
2006-07-26 15:00               ` Adrian Bunk [this message]
2006-07-26 15:07                 ` Andrew de Quincey
2006-07-26 17:11                 ` David Lang
2006-07-26 17:15 Chuck Ebbert

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=20060726150041.GG23701@stusta.de \
    --to=bunk@stusta.de \
    --cc=adq_dvb@lidskialf.net \
    --cc=apatard@mandriva.com \
    --cc=dlang@digitalinsight.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).