All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: sashiko-bot@kernel.org
Cc: "Zhao Feng" <zhaofeng2@cmss.chinamobile.com>,
	linux-mtd@lists.infradead.org,  sashiko-reviews@lists.linux.dev,
	richard@nod.at,  michal.simek@amd.com
Subject: Re: [PATCH 1/2] mtd: rawnand: fix GPIO descriptor leak in rawnand_dt_parse_gpio_cs()
Date: Tue, 17 Nov 2026 10:32:13 +0100	[thread overview]
Message-ID: <87eccjolb6.fsf@bootlin.com> (raw)
In-Reply-To: <sashiko-outbox-205535@kernel.org> (sashiko-bot@kernel.org's message of "Mon, 09 Nov 2026 20:05:33 +0000")

On 09/11/2026 at 20:05:33 GMT, sashiko-bot@kernel.org wrote:

> Thank you for your contribution! Sashiko AI review found no new issues
> in this patch, but noticed 1 related pre-existing issue it does not
> introduce:
> - [Medium] mtd: rawnand: arasan: GPIO descriptor leak in anfc_probe()
>   and anfc_parse_cs() [1]

I believe switching to the managed version like Sashiko proposes is a
better approach.

Can you please respin?

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2026-11-17  9:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  5:27 [PATCH 0/2] mtd: rawnand: fix GPIO CS descriptor leaks Zhao Feng
2026-11-09  5:27 ` Zhao Feng
2026-11-09  5:27 ` [PATCH 1/2] mtd: rawnand: fix GPIO descriptor leak in rawnand_dt_parse_gpio_cs() Zhao Feng
2026-11-09  5:27   ` Zhao Feng
2026-11-09 20:05   ` sashiko-bot
2026-11-17  9:32     ` Miquel Raynal [this message]
2026-11-09  5:27 ` [PATCH 2/2] mtd: rawnand: arasan: fix GPIO CS leak on probe error paths Zhao Feng
2026-11-09  5:27   ` Zhao Feng
2026-11-18  2:12 ` [PATCH v2 1/2] mtd: rawnand: parse GPIO CS with devm_gpiod_get_index_optional() zhaofeng2
2026-11-18  2:12   ` zhaofeng2
2026-11-18  2:12   ` [PATCH v2 2/2] mtd: rawnand: arasan: drop manual GPIO CS release zhaofeng2
2026-11-18  2:12     ` zhaofeng2

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=87eccjolb6.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michal.simek@amd.com \
    --cc=richard@nod.at \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zhaofeng2@cmss.chinamobile.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.