From: Arjan van de Ven <arjan@infradead.org>
To: David Lang <dlang@digitalinsight.com>
Cc: Andrew de Quincey <adq_dvb@lidskialf.net>,
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: Tue, 25 Jul 2006 18:56:58 +0200 [thread overview]
Message-ID: <1153846619.8932.36.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0607250945400.9159@qynat.qvtvafvgr.pbz>
On Tue, 2006-07-25 at 09:47 -0700, David Lang wrote:
> On Tue, 25 Jul 2006, Andrew de Quincey wrote:
>
> > On Tuesday 25 July 2006 10:55, Arnaud Patard wrote:
> >> Greg KH <gregkh@suse.de> writes:
> >>
> >> Hi,
> >>
> >>> We (the -stable team) are announcing the release of the 2.6.17.7 kernel.
> >>
> >> Sorry, but doesn't compile if DVB_BUDGET_AV is set :(
> >>
> >>> Andrew de Quincey:
> >>> v4l/dvb: Fix budget-av frontend detection
> >
> >
> > In fact it is just this patch causing the problem:
> <SNIP>
> > Sorry, I had so much work going on in that area I must have diffed the wrong
> > kernel when I created this patch. :(
>
> is it reasonable to have an aotomated test figure out what config options are
> relavent to a patch (or patchset) and test compile all the combinations to catch
> this sort of mistake?
well you can do such a thing withing statistical bounds; however... if
the patch already is in -git (as is -stable policy normally).. it should
have been found there already...
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
next prev parent reply other threads:[~2006-07-25 16:58 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 [this message]
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
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=1153846619.8932.36.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--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).