public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Jiri Kosina <trivial@kernel.org>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v5 00/13] pxa_camera transition to v4l2 standalone device
Date: Tue, 06 Sep 2016 10:49:44 +0200	[thread overview]
Message-ID: <87inu9if9z.fsf@belgarion.home> (raw)
In-Reply-To: <cb7496b2-cc64-7c6e-71b3-6c56e596c8dc@xs4all.nl> (Hans Verkuil's message of "Mon, 5 Sep 2016 14:40:05 +0200")

Hans Verkuil <hverkuil@xs4all.nl> writes:

> On 08/29/2016 07:55 PM, Robert Jarzmik wrote:
>> There is no change between v4 and v5, ie. the global diff is empty, only one
>> line was shifted to prevent breaking bisectablility.
>
> Against which tree do you develop? Unfortunately this patch series doesn't apply
> to the media_tree master branch anymore due to conflicts with a merged patch that
> converts s/g_crop to s/g_selection in all subdev drivers.
v4.8-rc1 is their base, so Linus's master.

> When you make the new patch series, please use the -M option with git send-email so
> patches that move files around are handled cleanly. That makes it much easier
> to review.
Ok.

> BTW, checkpatch reported issues in a switch statement in function
> pxa_camera_get_formats():
Yep, I noticed.

>         switch (code.code) {
>         case MEDIA_BUS_FMT_UYVY8_2X8:
>                 formats++;
>                 if (xlate) {
>                         xlate->host_fmt = &pxa_camera_formats[0];
>                         xlate->code     = code.code;
>                         xlate++;
>                         dev_dbg(dev, "Providing format %s using code %d\n",
>                                 pxa_camera_formats[0].name, code.code);
>                 }
>         case MEDIA_BUS_FMT_VYUY8_2X8:
>         case MEDIA_BUS_FMT_YUYV8_2X8:
>         case MEDIA_BUS_FMT_YVYU8_2X8:
>         case MEDIA_BUS_FMT_RGB565_2X8_LE:
>         case MEDIA_BUS_FMT_RGB555_2X8_PADHI_LE:
>                 if (xlate)
>                         dev_dbg(dev, "Providing format %s packed\n",
>                                 fmt->name);
>                 break;
>         default:
>                 if (!pxa_camera_packing_supported(fmt))
>                         return 0;
>                 if (xlate)
>                         dev_dbg(dev,
>                                 "Providing format %s in pass-through mode\n",
>                                 fmt->name);
>         }
>
> Before 'case MEDIA_BUS_FMT_VYUY8_2X8' should there be a break? If not, then
> there should be a '/* fall through */' comment.
There should have been a '/* fall through */' in the original code, even if that
was not strictly "required" at the time of writing.
>
> At the end of the default case there should also be a break statement.
>
> This is already in the existing code, so just make a separate patch fixing
> this.
Ok, will do.

Cheers.

--
Robert

      reply	other threads:[~2016-09-06  8:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 17:55 [PATCH v5 00/13] pxa_camera transition to v4l2 standalone device Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 01/13] media: mt9m111: make a standalone v4l2 subdevice Robert Jarzmik
2016-08-30  8:55   ` Guennadi Liakhovetski
2016-08-30 15:57     ` Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 02/13] media: mt9m111: use only the SRGB colorspace Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 03/13] media: mt9m111: move mt9m111 out of soc_camera Robert Jarzmik
2016-08-30  8:37   ` Guennadi Liakhovetski
2016-08-29 17:55 ` [PATCH v5 04/13] media: platform: pxa_camera: convert to vb2 Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 05/13] media: platform: pxa_camera: trivial move of functions Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 06/13] media: platform: pxa_camera: introduce sensor_call Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 07/13] media: platform: pxa_camera: make printk consistent Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 08/13] media: platform: pxa_camera: add buffer sequencing Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 09/13] media: platform: pxa_camera: remove set_crop Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 10/13] media: platform: pxa_camera: make a standalone v4l2 device Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 11/13] media: platform: pxa_camera: add debug register access Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 12/13] media: platform: pxa_camera: change stop_streaming semantics Robert Jarzmik
2016-08-29 17:55 ` [PATCH v5 13/13] media: platform: pxa_camera: move pxa_camera out of soc_camera Robert Jarzmik
2016-09-05 12:40 ` [PATCH v5 00/13] pxa_camera transition to v4l2 standalone device Hans Verkuil
2016-09-06  8:49   ` Robert Jarzmik [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=87inu9if9z.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=g.liakhovetski@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=trivial@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