public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: TJ <one.timothy.jones@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Pete Eberlein <pete@sensoray.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: go7007 driver -- which program you use for capture
Date: Thu, 14 Jan 2010 15:03:48 -0500	[thread overview]
Message-ID: <4B4F78A4.8000103@gmail.com> (raw)
In-Reply-To: <4B4E4550.7030907@redhat.com>


Mauro Carvalho Chehab wrote:
> It should be against -hg or linux-next tree, otherwise, I can't send it upstream.
> If you just want to send a patch for people to test, please mark it as RFC, otherwise
> I'll assume that you're sending a patch for upstream.
> 
> Since there are more people working on this driver, the better is to add what you
> have there, to avoid people to do a similar work.

OK my brother. I got a hold of the -hg tree and started working off of it.

Pete, Question: I was looking through the code and noticed that you turned s2250
driver into v4l2_subdev and go7007 driver initializes it as such and passes it
calls via call_all (v4l2_device_call_until_err). How does that affect other
drivers? Does that mean they all need to re-written as v4l2_subdev?

-TJ


  reply	other threads:[~2010-01-14 20:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08 19:07 go7007 driver -- which program you use for capture TJ
2010-01-08 20:17 ` Jarod Wilson
2010-01-08 22:25   ` TJ
2010-01-13 21:02     ` Mauro Carvalho Chehab
2010-01-13 22:04       ` TJ
2010-01-13 22:12         ` Mauro Carvalho Chehab
2010-01-14 20:03           ` TJ [this message]
2010-01-14 20:08             ` Pete Eberlein
2010-01-14 20:18               ` TJ
2010-01-12 23:46 ` Pete Eberlein
2010-01-13 21:51   ` TJ

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=4B4F78A4.8000103@gmail.com \
    --to=one.timothy.jones@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=pete@sensoray.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