Devicetree
 help / color / mirror / Atom feed
From: Antoine Bouyer <antoine.bouyer@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	julien.vuillaumier@nxp.com, alexi.birlinger@nxp.com,
	daniel.baluta@nxp.com, peng.fan@nxp.com, frank.li@nxp.com,
	jacopo.mondi@ideasonboard.com, laurent.pinchart@ideasonboard.com,
	mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, michael.riesch@collabora.com,
	anthony.mcgivern@arm.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	ai.luthra@ideasonboard.com, paul.elder@ideasonboard.com,
	geert@linux-m68k.org
Subject: Re: [PATCH v2 0/8] media: Add iMX95 neoisp driver
Date: Tue, 9 Jun 2026 17:09:46 +0200	[thread overview]
Message-ID: <8fa93d01-603c-4f1b-8d95-f44a27f00ab0@nxp.com> (raw)
In-Reply-To: <e15b9653-3d49-4300-9961-9303b983a4f5@kernel.org>

On 5/14/26 2:34 PM, Krzysztof Kozlowski wrote:
> 
> 
> On 11/05/2026 15:26, Antoine Bouyer wrote:
>>
>> ---
>> link to v1: https://lore.kernel.org/linux-media/20260413160331.2611829-1-antoine.bouyer@nxp.com/
>> Diff compared to v1:
>>   * Fix dt_binding_check errors reported by Rob's bot.
>>   * Remove extensible stats introduction, and use v4l2_isp patches
>>     from Jacopo's series instead.
>>   * Use the common v4l2_isp definitions for stats and params in neoisp.
>>     Replace all occurences of v4l2_isp_params_* and v4l2_isp_stats_* by
>>     the common structs and helpers.
>>   * Use the new v4l2_isp helpers for statistics buffer handling.
>>   * Apply comment from Geert in Kconfig.
>>   * Fix some typo in the neoisp documentation.
>>   * Remove `neoisp_feat_ctrl_s` from uapi (used only in legacy format
>>     which is not supported anymore).
>>
>> link to RFC: https://lore.kernel.org/linux-media/20260123080938.3367348-1-antoine.bouyer@nxp.com/
>> Diff compared to RFC:
> 
> This was v1. You even called it v1. This is v3. When you mess the
> numbers you make review unnecessary difficult.

Hi Krzysztof

Ok. Sorry for the mess. I will pay more attention next time.

To avoid further confusion in the numbering, I will prepare a v3 and 
keep the counter incrementing from there. I assume jumping now from v2 
to v4 would add even more confusion.

Please consider the RFC as a "v0" for this series.

Best regards
Antoine

> 
> Best regards,
> Krzysztof


      reply	other threads:[~2026-06-09 15:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 13:26 [PATCH v2 0/8] media: Add iMX95 neoisp driver Antoine Bouyer
2026-05-11 13:26 ` [PATCH v2 1/8] dt-bindings: media: Add nxp neoisp support Antoine Bouyer
2026-05-11 16:26   ` Conor Dooley
2026-05-13  8:39     ` Antoine Bouyer
2026-05-14 15:40   ` Rob Herring (Arm)
2026-05-11 13:26 ` [PATCH v2 2/8] media: v4l2-ctrls: Add user control base for NXP neoisp controls Antoine Bouyer
2026-05-11 13:26 ` [PATCH v2 3/8] media: Add meta formats supported by NXP neoisp driver Antoine Bouyer
2026-05-11 13:26 ` [PATCH v2 4/8] media: uapi: Add NXP NEOISP user interface header file Antoine Bouyer
2026-05-12  4:47   ` sashiko-bot
2026-05-11 13:26 ` [PATCH v2 5/8] media: Documentation: Add NXP neoisp driver documentation Antoine Bouyer
2026-05-12  5:04   ` sashiko-bot
2026-05-11 13:26 ` [PATCH v2 6/8] media: platform: Add NXP Neoisp Image Signal Processor Antoine Bouyer
2026-05-11 14:43   ` Antoine Bouyer
2026-05-12  5:29   ` sashiko-bot
2026-05-11 13:26 ` [PATCH v2 7/8] media: platform: neoisp: Add debugfs support Antoine Bouyer
2026-05-12  5:47   ` sashiko-bot
2026-05-11 13:26 ` [PATCH v2 8/8] arm64: dts: freescale: imx95: Add NXP neoisp device tree node Antoine Bouyer
2026-05-14 12:34 ` [PATCH v2 0/8] media: Add iMX95 neoisp driver Krzysztof Kozlowski
2026-06-09 15:09   ` Antoine Bouyer [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=8fa93d01-603c-4f1b-8d95-f44a27f00ab0@nxp.com \
    --to=antoine.bouyer@nxp.com \
    --cc=ai.luthra@ideasonboard.com \
    --cc=alexi.birlinger@nxp.com \
    --cc=anthony.mcgivern@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frank.li@nxp.com \
    --cc=geert@linux-m68k.org \
    --cc=imx@lists.linux.dev \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=julien.vuillaumier@nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=michael.riesch@collabora.com \
    --cc=paul.elder@ideasonboard.com \
    --cc=peng.fan@nxp.com \
    --cc=robh@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