All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
Cc: linux-staging@lists.linux.dev, Hans de Goede <hansg@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Andy Shevchenko <andy@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kees Cook <kees@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] staging: media: atomisp: clean up ia_css_stream_destroy
Date: Fri, 27 Mar 2026 10:48:15 +0300	[thread overview]
Message-ID: <acY2P24KESCLXA2g@stanley.mountain> (raw)
In-Reply-To: <20260326213442.876745-1-azpijr@gmail.com>

On Thu, Mar 26, 2026 at 10:34:06PM +0100, Jose A. Perez de Azpillaga wrote:
> This series fixes a loop shadowing bug and refactors the ISP2401 cleanup
> logic inside ia_css_stream_destroy().
> 
> Changes in v2:
> - Split the original patch into a 3-patch series as requested by
>   Dan Carpenter.
> - Added a Fixes tag for the loop shadowing bug.
> - Separated the extraction from the logical improvements.
> - Added clarification that assert() is a wrapper around BUG().

Thanks!

Reviewed-by: Dan Carpenter <dan.carpenter@linaro.org>

regards,
dan carpenter


      parent reply	other threads:[~2026-03-27  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 21:34 [PATCH v2 0/3] staging: media: atomisp: clean up ia_css_stream_destroy Jose A. Perez de Azpillaga
2026-03-26 21:34 ` [PATCH v2 1/3] staging: media: atomisp: fix loop shadowing in ia_css_stream_destroy() Jose A. Perez de Azpillaga
2026-03-26 21:34 ` [PATCH v2 2/3] staging: media: atomisp: extract ISP2401 cleanup into helper function Jose A. Perez de Azpillaga
2026-03-26 21:34 ` [PATCH v2 3/3] staging: media: atomisp: improve cleanup robustness in ia_css_stream_destroy_isp2401() Jose A. Perez de Azpillaga
2026-03-27  7:48 ` Dan Carpenter [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=acY2P24KESCLXA2g@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=andy@kernel.org \
    --cc=azpijr@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@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 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.