public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] V4L: mx3_camera: select VIDEOBUF2_DMA_CONTIG instead of VIDEOBUF_DMA_CONTIG
Date: Mon, 18 Apr 2011 09:27:59 +0100	[thread overview]
Message-ID: <20110418082759.GA25671@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110418082049.GJ3811@pengutronix.de>

On Mon, Apr 18, 2011 at 10:20:49AM +0200, Robert Schwebel wrote:
> Uwe,
> 
> On Mon, Apr 18, 2011 at 10:14:56AM +0200, Guennadi Liakhovetski wrote:
> > It's been pushed upstream almost 2 weeks ago:
> >
> > http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/31352
> 
> As our autobuilder does still trigger, I assume that the configs have to
> be refreshed and it may be an issue on our side. Can you take care of
> that?

Just take a look at what's in mainline:

config VIDEO_MX3
        tristate "i.MX3x Camera Sensor Interface driver"
        depends on VIDEO_DEV && MX3_IPU && SOC_CAMERA
        select VIDEOBUF_DMA_CONTIG
        select MX3_VIDEO
        ---help---
          This is a v4l2 driver for the i.MX3x Camera Sensor Interface

and you'll see that it hasn't made it there yet.  If I search for
'linuxtv.org' in the history post 2.6.39-rc2, there's no sign of it.

  reply	other threads:[~2011-04-18  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07  8:50 [PATCH] V4L: mx3_camera: select VIDEOBUF2_DMA_CONTIG instead of VIDEOBUF_DMA_CONTIG Uwe Kleine-König
2011-04-18  8:06 ` Uwe Kleine-König
2011-04-18  8:14   ` Guennadi Liakhovetski
2011-04-18  8:20     ` Robert Schwebel
2011-04-18  8:27       ` Russell King - ARM Linux [this message]
2011-04-18  8:45       ` Uwe Kleine-König

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=20110418082759.GA25671@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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