linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 11/18] v4l: vsp1: wpf: Simplify cast to pipeline structure
Date: Sun, 01 Jun 2014 14:47:55 +0200	[thread overview]
Message-ID: <20315353.bdlSXH88Rv@avalon> (raw)
In-Reply-To: <CAMuHMdUCT1rSQWn+B9zQ3a-BPJsBePK9K5NszR==AriaRm8BjQ@mail.gmail.com>

Hi Geert,

On Sunday 01 June 2014 10:50:20 Geert Uytterhoeven wrote:
> On Sun, Jun 1, 2014 at 5:39 AM, Laurent Pinchart wrote:
> > USe the subdev pointer directly to_vsp1_pipeline() macro instead of
> 
> Use

Thank you. I'll fix that for the next version. I would be happy this typo was 
the biggest issue with the patch set :-)

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-06-01 12:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01  3:39 [PATCH 00/18] Renesas VSP1: alpha support Laurent Pinchart
2014-06-01  3:39 ` [PATCH 01/18] v4l: Add ARGB and XRGB pixel formats Laurent Pinchart
2014-06-01  3:39 ` [PATCH 02/18] DocBook: media: Document ALPHA_COMPONENT control usage on output devices Laurent Pinchart
2014-06-01  3:39 ` [PATCH 03/18] v4l: Support extending the v4l2_pix_format structure Laurent Pinchart
2014-06-01  3:39 ` [PATCH 04/18] v4l: Add premultiplied alpha flag for pixel formats Laurent Pinchart
2014-06-01  3:39 ` [PATCH 05/18] v4l: vsp1: Fix typos Laurent Pinchart
2014-06-01  3:39 ` [PATCH 06/18] v4l: vsp1: Cleanup video nodes at removal time Laurent Pinchart
2014-06-01  3:39 ` [PATCH 07/18] v4l: vsp1: Propagate vsp1_device_get errors to the callers Laurent Pinchart
2014-06-01  3:39 ` [PATCH 08/18] v4l: vsp1: Setup control handler automatically at stream on time Laurent Pinchart
2014-06-01  3:39 ` [PATCH 09/18] v4l: vsp1: sru: Fix the intensity control default value Laurent Pinchart
2014-06-01  3:39 ` [PATCH 10/18] v4l: vsp1: sru: Make the intensity controllable during streaming Laurent Pinchart
2014-06-01  3:39 ` [PATCH 11/18] v4l: vsp1: wpf: Simplify cast to pipeline structure Laurent Pinchart
2014-06-01  8:50   ` Geert Uytterhoeven
2014-06-01 12:47     ` Laurent Pinchart [this message]
2014-06-01  3:39 ` [PATCH 12/18] v4l: vsp1: wpf: Clear RPF to WPF association at stream off time Laurent Pinchart
2014-06-01  3:39 ` [PATCH 13/18] v4l: vsp1: Switch to XRGB formats Laurent Pinchart
2014-06-01  3:39 ` [PATCH 14/18] v4l: vsp1: Add alpha channel support to the memory ports Laurent Pinchart
2014-06-01  3:39 ` [PATCH 15/18] v4l: vsp1: Add V4L2_CID_ALPHA_COMPONENT control support Laurent Pinchart
2014-06-01  3:39 ` [PATCH 16/18] v4l: vsp1: bru: Support premultiplied alpha at the BRU inputs Laurent Pinchart
2014-06-01  3:39 ` [PATCH 17/18] v4l: vsp1: bru: Support non-premultiplied colors at the BRU output Laurent Pinchart
2014-06-01  3:39 ` [PATCH 18/18] v4l: vsp1: bru: Make the background color configurable Laurent Pinchart
2014-06-01  8:51 ` [PATCH 00/18] Renesas VSP1: alpha support Geert Uytterhoeven
2014-06-01  8:56   ` Geert Uytterhoeven
2014-06-01 10:31     ` Laurent Pinchart

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=20315353.bdlSXH88Rv@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).