[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aV5sC_udoJ3qdjBD@stanley.mountain>
Date: Wed, 7 Jan 2026 17:22:03 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Karthikey D Kadati <karthikey3608@...il.com>
Cc: Hans de Goede <hansg@...nel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 RESEND 0/3] media: atomisp: refactoring and fixes for
V4L2 compliance
When you're sending v2, it's better to just start a new thread. We stopped
sending them as a reply years ago. It makes threads too confusing.
On Wed, Jan 07, 2026 at 07:18:41PM +0530, Karthikey D Kadati wrote:
> This patch series addresses maintainer feedback and fixes build errors
> in the atomisp driver.
>
> Patch 1: Standardizes the 'Bridge' structs significantly by using v4l2_rect instead of custom shadow structs and aligning ia_css_region members with V4L2 conventions.
> Patch 2: Introduces a helper function for statistics buffer allocation to reduce code duplication and centralize error handling logic.
> Patch 3: Adds missing error propagation for IRQ enable and XNR configuration to improve robustness.
>
Please line wrap your emails at 72 characters.
regards,
dan carpenter
Powered by blists - more mailing lists