public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: bumkunjo@gmx.de
To: linux-dvb@linuxtv.org
Cc: stev391@email.com
Subject: Re: [linux-dvb] [PATCH] Add initial support for DViCO FusionHDTV DVB-T Dual Express
Date: Fri, 1 Aug 2008 14:34:49 +0200	[thread overview]
Message-ID: <200808011434.49919.bumkunjo@gmx.de> (raw)
In-Reply-To: <20080801034025.C0EC947808F@ws1-5.us4.outblaze.com>


if more testers are welcome / needed you may contact me too.

Regards, Jochen

Am Freitag 01 August 2008 05:40:25 schrieb stev391@email.com:
>  Anton,
>
> Thankyou for cleaning this code up (and you as well Steven).
>
> I have been meaning to do some more work on this lately, but you have
> taken it to were I was hoping to go.
>
> Steven, I can test your cleaned up code as well, just drop me an email
> and I will run it on my machines (I have several that I have access to
> with these cards in them, with various other cards).
>
> Regards,
>
> Stephen.
>
>   ----- Original Message -----
>   From: "Anton Blanchard"
>   To: "Steven Toth"
>   Subject: Re: [linux-dvb] [PATCH] Add initial support for DViCO
>   FusionHDTV DVB-T Dual Express
>   Date: Fri, 1 Aug 2008 12:55:13 +1000
>
>
>
>   Hi,
>
>   > At this stage I think I can add a final patch to get back to a
>   > single callback directly, regardless of tuner type. (this
>   > weekend)
>
>   Great!
>
>   > I don't have your specific DViCO card, I assume you're willing to
>   > re-test with my cleanup patch?
>
>   Yep I have the card and will re-test.
>
>   Anton

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-08-01 12:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01  3:40 [linux-dvb] [PATCH] Add initial support for DViCO FusionHDTV DVB-T Dual Express stev391
2008-08-01 12:34 ` bumkunjo [this message]
2008-08-05  1:25 ` Steven Toth
     [not found]   ` <1217969890.6864.11.camel@bonnie>
2008-08-05 21:16     ` Steven Toth
2008-08-05 21:43   ` Anton Blanchard
2008-08-05 23:41     ` Luke Yelavich
2008-08-06  1:44       ` Steven Toth
2008-08-06  8:09         ` David Porter
2008-08-06  8:51           ` Tim Farrington
2008-08-07  3:31             ` David
2008-08-07  4:34               ` Tim Farrington
2008-08-07  6:41                 ` David
2008-08-07  7:00                   ` Tim Farrington
2008-08-07  7:10                     ` David
2008-08-07  7:18                       ` SUBHRANIL CHOUDHURY
2008-08-07  7:52                       ` Tim Farrington
2008-08-07  8:47                         ` David
2008-08-10 23:31         ` Luke Yelavich
2008-08-07  1:06     ` jochen s
  -- strict thread matches above, loose matches on Subject: below --
2008-08-08  0:04 stev391
2008-08-07 10:58 stev391
2008-08-07 15:00 ` Steven Toth
2008-08-16  4:28 ` David
2008-08-05 11:52 stev391
2008-06-30 23:56 stev391
     [not found] ` <20080731042433.GA21788@kryten>
2008-07-31 15:08   ` Steven Toth
2008-08-01  1:21     ` Anton Blanchard
2008-08-01  1:43       ` Steven Toth
2008-08-01  2:04       ` Steven Toth
2008-08-01  2:13         ` Anton Blanchard
2008-08-01  2:52           ` Steven Toth
2008-08-01  2:55             ` Anton Blanchard

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=200808011434.49919.bumkunjo@gmx.de \
    --to=bumkunjo@gmx.de \
    --cc=linux-dvb@linuxtv.org \
    --cc=stev391@email.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