From: Jean Delvare <khali@linux-fr.org>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: David Lang <dlang@digitalinsight.com>,
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,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: automated test? (was Re: Linux 2.6.17.7)
Date: Tue, 25 Jul 2006 20:42:36 +0200 [thread overview]
Message-ID: <20060725204236.2afae33d.khali@linux-fr.org> (raw)
In-Reply-To: <44C64FC1.4060501@linuxtv.org>
Hi Michael,
> The fix can be found here... We'll need this queued up for 2.6.17.8 ...
> I have already attached this inline in a prior email, not sure how many
> people have seen that yet...
>
> You can also get it from here:
>
> http://linuxtv.org/~mkrufky/stable/2.6.17.y/budget-av-compile-fix.patch
Yes, it fixed the compilation cleanly for me (on both i386 and x86_64).
I can't test beyond that though, as I don't have that specific hardware.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2006-07-25 18:42 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20060725204236.2afae33d.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=adq_dvb@lidskialf.net \
--cc=apatard@mandriva.com \
--cc=arjan@infradead.org \
--cc=dlang@digitalinsight.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@linuxtv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.