public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, linux-media@vger.kernel.org,
	rafael@kernel.org, heikki.krogerus@linux.intel.com
Subject: Re: [PATCH v4 2/8] ACPI: property: Parse _CRS CSI-2 descriptor
Date: Wed, 8 Feb 2023 18:43:36 +0200	[thread overview]
Message-ID: <Y+PROE+7o8yuoGB6@smile.fi.intel.com> (raw)
In-Reply-To: <20230208152807.3064242-3-sakari.ailus@linux.intel.com>

On Wed, Feb 08, 2023 at 05:28:01PM +0200, Sakari Ailus wrote:
> Parse newly added ACPI _CRS CSI-2 descriptor for CSI-2 and camera
> configuration. For now, only figure out where the descriptor is present in
> order to allow adding information from it to related devices.

Nit-picks below that may be ignored. Up to you, guys.

...

> +#define NO_CSI2_PORT (~1U)

A bit unclear why this value. Is it bitfield? Then GENMASK() would be better.
Is it a plain value with a type limit? Then (UINT_MAX - 1) probably the best.

...

> +	ads->nodeptrs = (void *)(ads->nodes +
> +				 ports_count * 2 + 1);

Now this fits one line.

...

> +	handle_refs = kcalloc(csi2_all.handle_count + 1, sizeof(*handle_refs),
> +			      GFP_KERNEL);
> +	if (!handle_refs) {
> +		acpi_handle_debug(handle, "no memory for %zu handle refs\n",
> +				  csi2_all.handle_count + 1);
> +		return;
> +	}

In a code above you used "1 + foo" approach if I'm not mistaken. Why here is
the difference?

...

In some code comments which I removed before remarking you forgot the
grammatical period.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-02-08 16:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 15:27 [PATCH v4 0/8] ACPI _CRS CSI-2 and MIPI DisCo for Imaging support Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 1/8] ACPI: property: Parse data node string references in properties Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 2/8] ACPI: property: Parse _CRS CSI-2 descriptor Sakari Ailus
2023-02-08 16:43   ` Andy Shevchenko [this message]
2023-02-08 20:26     ` Sakari Ailus
2023-02-08 20:43   ` kernel test robot
2023-02-08 22:16     ` Sakari Ailus
2023-02-08 21:04   ` kernel test robot
2023-02-09  2:43     ` Philip Li
2023-02-08 15:28 ` [PATCH v4 3/8] device property: Add SOFTWARE_NODE() macro for defining software nodes Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 4/8] ACPI: property: Generate camera swnodes for ACPI and DisCo for Imaging Sakari Ailus
2023-02-08 16:48   ` Andy Shevchenko
2023-02-08 15:28 ` [PATCH v4 5/8] ACPI: property: Dig "rotation" property for devices with CSI2 _CRS Sakari Ailus
2023-02-08 16:51   ` Andy Shevchenko
2023-02-08 20:56     ` Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 6/8] ACPI: property: Rename parsed MIPI DisCo for Imaging properties Sakari Ailus
2023-02-08 16:56   ` Andy Shevchenko
2023-02-08 21:27     ` Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 7/8] ACPI: property: Skip MIPI property table without "mipi-img" prefix Sakari Ailus
2023-02-08 15:28 ` [PATCH v4 8/8] ACPI: property: Document _CRS CSI-2 and DisCo for Imaging support Sakari Ailus

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=Y+PROE+7o8yuoGB6@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox