All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 3/3] gpu: ipu-v3: Move i.MX IPUv3 core driver out of staging
Date: Thu, 27 Feb 2014 20:41:36 +0000	[thread overview]
Message-ID: <20140227204136.GA7649@kroah.com> (raw)
In-Reply-To: <1393328624-28013-5-git-send-email-p.zabel@pengutronix.de>

On Tue, Feb 25, 2014 at 01:09:57PM +0100, Philipp Zabel wrote:
> Am Dienstag, den 25.02.2014, 12:43 +0100 schrieb Philipp Zabel:
> > The i.MX Image Processing Unit (IPU) contains a number of image processing
> > blocks that sit right in the middle between DRM and V4L2. Some of the modules,
> > such as Display Controller, Processor, and Interface (DC, DP, DI) or CMOS
> > Sensor Interface (CSI) and their FIFOs could be assigned to either framework,
> > but others, such as the dma controller (IDMAC) and image converter (IC) can
> > be used by both.
> > The IPUv3 core driver provides an internal API to access the modules, to be
> > used by both DRM and V4L2 IPUv3 drivers.
> [...]
> 
> This one is missing:
> 
> diff --git a/drivers/staging/imx-drm/imx-hdmi.c b/drivers/staging/imx-drm/imx-hdmi.c
> index cb4eb76..9aeb863 100644
> --- a/drivers/staging/imx-drm/imx-hdmi.c
> +++ b/drivers/staging/imx-drm/imx-hdmi.c
> @@ -28,7 +28,8 @@
>  #include <drm/drm_edid.h>
>  #include <drm/drm_encoder_slave.h>
>  
> -#include "ipu-v3/imx-ipu-v3.h"
> +#include <video/imx-ipu-v3.h>
> +

What do you mean?  I can't apply this patch?

Totally confused,

greg k-h

  parent reply	other threads:[~2014-02-27 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 11:43 [PATCH 3/3] gpu: ipu-v3: Move i.MX IPUv3 core driver out of staging Philipp Zabel
2014-02-25 12:09 ` Philipp Zabel
2014-02-27 20:41 ` Greg Kroah-Hartman [this message]
2014-02-27 20:49 ` 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=20140227204136.GA7649@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@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 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.