All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org,
	Volokh Konstantin <volokh84@gmail.com>,
	Pete Eberlein <pete@sensoray.com>
Subject: Re: [GIT PULL FOR v3.10] go7007 driver overhaul
Date: Mon, 25 Mar 2013 08:10:01 -0300	[thread overview]
Message-ID: <20130325081001.18f72507@redhat.com> (raw)
In-Reply-To: <20130325080654.20e6c746@redhat.com>

Em Mon, 25 Mar 2013 08:06:54 -0300
Mauro Carvalho Chehab <mchehab@redhat.com> escreveu:

> Em Mon, 25 Mar 2013 10:02:29 +0100
> Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> 
> > On Sun March 24 2013 17:13:40 Mauro Carvalho Chehab wrote:
> > > Em Fri, 22 Mar 2013 15:36:35 +0100
> > > Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> > > 
> ...
> > > >       saa7134-go7007: add support for this combination.
> > > 
> > > I won't apply this one yet. A non-staging driver should not try to load a
> > > staging one without a notice. That change would be ok if you were also
> > > moving go7007 out of staging.
> > 
> > Fair enough. I will prepare a patch that at least updates the saa7134-go7007.c
> > source with my changes. That only leaves the patch to saa7134 itself that will
> > need to be applied once this driver goes out of staging.
> 
> Ok.
> 
> > > 
> > > >       s2250: add comment describing the hardware.
> > > >       go7007-loader: renamed from s2250-loader
> > > >       go7007-loader: add support for the other devices and move fw files
> > > >       go7007: update the README
> > > 
> > > You need to add there:
> > > 	- move cypress load firmware to drivers/media/common;
> > > 
> > > And some note about saa7134 integration.
> > 
> > Would it be OK if I add the saa7134 patch to the go7007 directory? Rather
> > than keeping it around in my git tree?
> 
> What do you mean? Adding a diff file there? If so, that sounds weird. If you're
> afraid of losing it, post it at the ML as RFC instead and add a pointer to the
> patchwork number for such RFC patch at README.

Never mind. I saw the patch. While it looks a little ugly, I'll apply.

Cheers,
Mauro

      reply	other threads:[~2013-03-25 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 14:36 [GIT PULL FOR v3.10] go7007 driver overhaul Hans Verkuil
2013-03-24 16:13 ` Mauro Carvalho Chehab
2013-03-25  9:02   ` Hans Verkuil
2013-03-25 11:06     ` Mauro Carvalho Chehab
2013-03-25 11:10       ` Mauro Carvalho Chehab [this message]

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=20130325081001.18f72507@redhat.com \
    --to=mchehab@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=pete@sensoray.com \
    --cc=volokh84@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.