All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	linux-media@vger.kernel.org, Jacopo Mondi <jacopo@jmondi.org>,
	Xavier Roumegue <xavier.roumegue@oss.nxp.com>,
	linux-imx@nxp.com, kernel@pengutronix.de
Subject: Re: [PATCH 4/7] media: v4l2: Make colorspace validity checks more future-proof
Date: Thu, 30 Jun 2022 12:48:10 +0300	[thread overview]
Message-ID: <Yr1xWpyR37kPcM0c@pendragon.ideasonboard.com> (raw)
In-Reply-To: <Yr1w6Pt7mGpz+XWv@valkosipuli.retiisi.eu>

On Thu, Jun 30, 2022 at 12:46:16PM +0300, Sakari Ailus wrote:
> On Wed, Jun 29, 2022 at 03:50:47PM +0200, Hans Verkuil wrote:
> > > @@ -585,8 +585,8 @@ static inline bool v4l2_is_hsv_enc_valid(__u8 hsv_enc)
> > >  
> > >  static inline bool v4l2_is_quant_valid(__u8 quantization)
> > >  {
> > > -	return quantization == V4L2_QUANTIZATION_FULL_RANGE ||
> > > -	       quantization == V4L2_QUANTIZATION_LIM_RANGE;
> > > +	return quantization > V4L2_QUANTIZATION_DEFAULT &&
> > > +	       quantization < V4L2_QUANTIZATION_LAST;
> > 
> > There are only two quantization ranges: full and limited. And I very sincerely
> > hope there will never be a third!
> 
> For consistency of the checks and definitions I prefer it how it's in the
> patch. There's no functional difference though.

I'm ready to send a pull request for this patch once you and Hans agree
on how this should be done :-) I also have a slight preference for
consistency. Hans, what do you think ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2022-06-30  9:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 18:36 [PATCH 0/7] media: nxp: i.MX8 ISI driver Laurent Pinchart
2022-06-16 18:36 ` [PATCH 1/7] media: v4l: Add packed YUV 4:4:4 YUVA and YUVX pixel formats Laurent Pinchart
2022-06-29 13:46   ` Hans Verkuil
2022-06-16 18:36 ` [PATCH 2/7] media: v4l2-tpg: Add support for the new YUVA and YUVX formats Laurent Pinchart
2022-06-28 10:22   ` Jacopo Mondi
2022-06-29 13:47   ` Hans Verkuil
2022-06-16 18:36 ` [PATCH 3/7] media: vivid: " Laurent Pinchart
2022-06-27 23:53   ` Laurent Pinchart
2022-06-28 10:28   ` Jacopo Mondi
2022-06-29 13:47   ` Hans Verkuil
2022-06-29 13:54   ` Hans Verkuil
2022-06-30  0:17     ` Laurent Pinchart
2022-06-16 18:36 ` [PATCH 4/7] media: v4l2: Make colorspace validity checks more future-proof Laurent Pinchart
2022-06-29 13:50   ` Hans Verkuil
2022-06-30  9:46     ` Sakari Ailus
2022-06-30  9:48       ` Laurent Pinchart [this message]
2022-06-30  9:56         ` Hans Verkuil
2022-06-16 18:36 ` [PATCH 5/7] media: v4l2: Sanitize colorspace values in the framework Laurent Pinchart
2022-06-29 13:59   ` Hans Verkuil
2022-06-16 18:36 ` [PATCH 6/7] dt-bindings: media: Add i.MX8 ISI DT bindings Laurent Pinchart
2022-06-17  2:47   ` Rob Herring
2022-06-16 18:36 ` [PATCH 7/7] media: nxp: Add i.MX8 ISI driver Laurent Pinchart
2022-06-17  2:40   ` kernel test robot

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=Yr1xWpyR37kPcM0c@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jacopo@jmondi.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=xavier.roumegue@oss.nxp.com \
    /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.