All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Brue <ryanbrue.dev@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: conor+dt@kernel.org, mfd@lists.linux.dev, robh@kernel.org,
	devicetree@vger.kernel.org, lee@kernel.org
Subject: Re: [PATCH v2 2/3] iio: adc: mt6397-auxadc: add mt6397 PMIC AUXADC driver
Date: Thu, 17 Sep 2026 21:44:43 -0500	[thread overview]
Message-ID: <3b4dc4b5-4e54-4a8a-b6d5-7177f341dbcc@gmail.com> (raw)
In-Reply-To: <20260918022714.1B1591F00893@smtp.kernel.org>

On 9/17/26 9:27 PM, sashiko-bot@kernel.org wrote:
> [Severity: Low]
> Does this mix scope-based guard() for locking with goto-based error handling
> in mt6397_auxadc_read_channel()?
>
> While this might not cause a direct functional bug in this exact instance
> since the lock is held across the entire function scope and released
> correctly, it explicitly violates the kernel cleanup subsystem rules in
> include/linux/cleanup.h.
>
> The cleanup guidelines mandate that goto and cleanup helpers should never be
> mixed in the same function to avoid introducing an anti-pattern that creates
> confusing ownership semantics.
>
> [ ... ]
>
Whoops, yeah, I introduced that while fixing the teardown when the setup 
fails part-way. I can fix it in a v3. Depending on the timing of Luca's 
patches, I will probably have to do a v3 anyways. I'll wait for more 
human reviews before spinning up a v3 though. Don't want to spam the 
mailing list :)

Best regards,
Ryan

  reply	other threads:[~2026-09-18  2:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  2:19 [PATCH v2 0/3] iio: adc: add mt6397 PMIC AUXADC support Ryan Brue
2026-09-18  2:19 ` [PATCH v2 1/3] dt-bindings: iio: adc: mediatek,mt6359-auxadc: add mt6397 PMIC AUXADC Ryan Brue
2026-09-18  2:25   ` sashiko-bot
2026-09-18  2:19 ` [PATCH v2 2/3] iio: adc: mt6397-auxadc: add mt6397 PMIC AUXADC driver Ryan Brue
2026-09-18  2:27   ` sashiko-bot
2026-09-18  2:44     ` Ryan Brue [this message]
2026-09-18  7:31   ` Andy Shevchenko
2026-09-20  2:48     ` Ryan Brue
2026-09-18  2:19 ` [PATCH v2 3/3] mfd: mt6397-core: Add mt6397 AUXADC support Ryan Brue
2026-09-18  2:28   ` sashiko-bot
2026-09-18  7:18 ` [PATCH v2 0/3] iio: adc: add mt6397 PMIC " Andy Shevchenko
2026-09-20  5:18   ` Ryan Brue

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=3b4dc4b5-4e54-4a8a-b6d5-7177f341dbcc@gmail.com \
    --to=ryanbrue.dev@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lee@kernel.org \
    --cc=mfd@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.