From: "Németh Márton" <nm127@freemail.hu>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: OK
Date: Sun, 07 Mar 2010 13:20:16 +0100 [thread overview]
Message-ID: <4B939A00.5090208@freemail.hu> (raw)
In-Reply-To: <201003061952.o26JqdTY011655@smtp-vbr11.xs4all.nl>
Hello Hans,
Hans Verkuil wrote:
> This message is generated daily by a cron job that builds v4l-dvb for
> the kernels and architectures in the list below.
Would you mind adding a new test case for your test environment? This would
be a test case with the newest stable kernel without Power Management support
(CONFIG_PM not defined in .config). It seems some problem could be caught with
this test case.
Regards,
Márton Németh
next prev parent reply other threads:[~2010-03-07 12:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 19:52 [cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: OK Hans Verkuil
2010-03-07 5:49 ` Németh Márton
2010-03-07 9:52 ` Hans Verkuil
2010-03-07 12:20 ` Németh Márton [this message]
2010-03-07 12:29 ` Hans Verkuil
2010-03-07 13:00 ` Németh Márton
-- strict thread matches above, loose matches on Subject: below --
2010-03-10 20:30 Hans Verkuil
2010-03-08 20:05 Hans Verkuil
2010-03-07 20:05 Hans Verkuil
2010-03-02 19:52 Hans Verkuil
2010-03-01 19:53 Hans Verkuil
2010-01-13 19:58 Hans Verkuil
2010-01-12 19:58 Hans Verkuil
2010-01-11 19:58 Hans Verkuil
2010-01-10 19:58 Hans Verkuil
2010-01-09 19:50 Hans Verkuil
2010-01-08 19:50 Hans Verkuil
2010-01-07 19:50 Hans Verkuil
2010-01-06 19:50 Hans Verkuil
2010-01-05 19:50 Hans Verkuil
2010-01-04 19:50 Hans Verkuil
2010-01-03 19:50 Hans Verkuil
2010-01-02 19:50 Hans Verkuil
2010-01-01 19:50 Hans Verkuil
2009-12-31 19:50 Hans Verkuil
2009-12-30 19:55 Hans Verkuil
2009-12-29 19:59 Hans Verkuil
2009-12-29 21:21 ` Németh Márton
2009-12-29 22:47 ` Mauro Carvalho Chehab
2009-12-29 23:17 ` Németh Márton
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=4B939A00.5090208@freemail.hu \
--to=nm127@freemail.hu \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.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