public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@kernellabs.com>
To: urishk@yahoo.com, Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Recent Siano patches - testing required
Date: Tue, 19 May 2009 15:15:46 -0400	[thread overview]
Message-ID: <4A130562.105@kernellabs.com> (raw)

Mauro please review.

Uri,

Firstly I'd like to thank you and Siano for patching and helping to maintain the 
driver. :)

Second, this is a heck of a lot of change for the list to review! It's 
impossible to digest the level of rework and potential regressions.

I'd suggest you either host your own mercurial server and have testers pull your 
trees, helping to regression test your changes or ... someone gives you access 
to create trees at LinuxTV.org, then you can solicit testers feedback on the 
mailing list.

Either way, it's unusual for this amount of change to be merged without having 
some positive feedback from the Linux community of testers. If you have 
confirmation that all of the current devices are still working correct, without 
regression, then please indicate this in your patches / email.

If not, the patches should be hosted somewhere for test and review.

-- 
Steven Toth - Kernel Labs
http://www.kernellabs.com

             reply	other threads:[~2009-05-19 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 19:15 Steven Toth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-19 20:10 Recent Siano patches - testing required Uri Shkolnik
2009-05-19 21:30 ` Steven Toth
2009-05-20  1:35   ` Mauro Carvalho Chehab
2009-05-20  2:05     ` Devin Heitmueller
2009-05-20  2:05       ` hermann pitton
2009-05-20  4:06       ` Mauro Carvalho Chehab
2009-05-20  2:44     ` Steven Toth

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=4A130562.105@kernellabs.com \
    --to=stoth@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=urishk@yahoo.com \
    /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