public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "istvan_v@mailbox.hu" <istvan_v@mailbox.hu>
To: unlisted-recipients:; (no To-header on input)@bombadil.infradead.org
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] DTV2000 H Plus issues
Date: Sun, 14 Mar 2010 18:50:43 +0100	[thread overview]
Message-ID: <4B9D21F3.8090902@mailbox.hu> (raw)
In-Reply-To: <4B7C84F3.4080708@redhat.com>

OK, so should I write a new xc4000.c/h from scratch and sign that off ?

On 02/18/2010 01:08 AM, Mauro Carvalho Chehab wrote:

> Devin Heitmueller wrote:
>> On Wed, Feb 17, 2010 at 6:51 PM, Mauro Carvalho Chehab
>> <mchehab@redhat.com> wrote:
>>> Hi Istvan,
>>>
>>> istvan_v@mailbox.hu wrote:
>>>> The attached new patches contain all the previous changes merged, and
>>>> are against the latest v4l-dvb revision.
>>> Please provide your Signed-off-by. This is a basic requirement for your
>>> driver to be accepted. Please read:
>>>        http://linuxtv.org/hg/v4l-dvb/raw-file/tip/README.patches
>>>
>>> for instructions on how to submit a patch.
>>
>> Hi Mauro,
>>
>> I would hate to come across as a jerk here, but he cannot provide his
>> SOB for this patch, as I wrote about 95% of the code here.  It's
>> derived from a tree I have been working on for the PCTV 340e:
>>
>> http://kernellabs.com/hg/~dheitmueller/pctv-340e-2/
>>
>> I know that istvan wants to see the support merged, but he is going to
>> have to wait a bit longer since he is not the author or maintainer of
>> the driver in question.
> 
> OK. Then, I need your SOB for the 95% of the code, and his SOB for the
> remaining ;)

  parent reply	other threads:[~2010-03-14 17:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-02 16:10 DTV2000 H Plus issues Raena Lea-Shannon
2010-01-02 16:57 ` istvan_v
2010-01-03  8:21   ` Raena Lea-Shannon
2010-01-03 11:31     ` Samuel Rakitnican
2010-01-04 13:01       ` Raena Lea-Shannon
2010-01-04 16:48     ` istvan_v
2010-01-05  1:25       ` Raena Lea-Shannon
2010-01-07 19:49         ` istvan_v
2010-01-07 20:00           ` Devin Heitmueller
2010-01-07 21:07             ` istvan_v
2010-02-09 17:35           ` istvan_v
2010-02-11 19:16             ` istvan_v
2010-02-11 19:21               ` Devin Heitmueller
2010-02-11 19:35                 ` istvan_v
2010-02-12 18:26               ` istvan_v
2010-02-12 18:34                 ` istvan_v
2010-02-17 18:06               ` [PATCH] " istvan_v
2010-02-17 23:51                 ` Mauro Carvalho Chehab
2010-02-17 23:59                   ` Devin Heitmueller
2010-02-18  0:08                     ` Mauro Carvalho Chehab
2010-02-18  0:11                       ` Devin Heitmueller
2010-03-14 17:58                         ` istvan_v
2010-03-15  4:15                           ` Devin Heitmueller
2010-03-16 18:24                             ` istvan_v
2010-03-22 18:33                             ` istvan_v
2010-03-24 11:38                               ` istvan_v
2010-03-14 17:50                       ` istvan_v [this message]
2010-02-19 19:54                     ` istvan_v
2010-03-10 23:17                       ` istvan_v

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=4B9D21F3.8090902@mailbox.hu \
    --to=istvan_v@mailbox.hu \
    --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