public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [media-ctl PATCH 1/1] media-ctl: Compose print fixes
Date: Mon, 28 May 2012 17:58:35 +0200	[thread overview]
Message-ID: <1370836.N3WTkptTkm@avalon> (raw)
In-Reply-To: <1338050597-19251-1-git-send-email-sakari.ailus@iki.fi>

Hi Sakari,

On Saturday 26 May 2012 19:43:16 Sakari Ailus wrote:
> The compose rectangles were printed incorrectly in my recent patch "Compose
> rectangle support for libv4l2subdev" without parenthesis. Fix this.
> 
> Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi>
> ---
> Hi Laurent,
> 
> Could you apply this simple fix to your tree? Currently the compose
> rectangles are printed differently than the crop rectangles which certainly
> isn't the intention.

Done, thank you.

>  src/main.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/src/main.c b/src/main.c
> index af16818..d10094b 100644
> --- a/src/main.c
> +++ b/src/main.c
> @@ -81,14 +81,14 @@ static void v4l2_subdev_print_format(struct media_entity
> *entity, V4L2_SUBDEV_SEL_TGT_COMPOSE_BOUNDS,
>  					which);
>  	if (ret == 0)
> -		printf("\n\t\t compose.bounds:%u,%u/%ux%u",
> +		printf("\n\t\t compose.bounds:(%u,%u)/%ux%u",
>  		       rect.left, rect.top, rect.width, rect.height);
> 
>  	ret = v4l2_subdev_get_selection(entity, &rect, pad,
>  					V4L2_SUBDEV_SEL_TGT_COMPOSE_ACTUAL,
>  					which);
>  	if (ret == 0)
> -		printf("\n\t\t compose:%u,%u/%ux%u",
> +		printf("\n\t\t compose:(%u,%u)/%ux%u",
>  		       rect.left, rect.top, rect.width, rect.height);
> 
>  	printf("]\n");

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2012-05-28 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26 16:43 [media-ctl PATCH 1/1] media-ctl: Compose print fixes Sakari Ailus
2012-05-28 15:58 ` Laurent Pinchart [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=1370836.N3WTkptTkm@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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