From: Mark Brown <broonie@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v3 0/7] regmap: cleanups for regcache and regmap init paths
Date: Wed, 7 Oct 2026 15:23:05 +0200 [thread overview]
Message-ID: <asZHudwIW5QkdhCg@sirena.co.uk> (raw)
In-Reply-To: <20261007-regmap-lock-2nd-v3-0-0e590c4125be@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
On Wed, Oct 07, 2026 at 08:03:56PM +0800, Peng Fan (OSS) wrote:
> Following up the previous regmap guard lock patchset [1].
>
> [1] https://lore.kernel.org/all/179062150526.139547.3870545428656485907.b4-ty@b4/#r
>
> This is the 2nd batch to do more cleanup.
>
> This series tidies up locking, error handling, and resource management
> across the regmap core and regcache.
I applied v2, please send an incremental change with the fix for the
goto issue.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-07 13:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 12:03 Peng Fan (OSS)
2026-10-07 12:03 ` [PATCH v3 1/7] regcache: extract locked helpers to replace open-coded lock/unlock pairs Peng Fan (OSS)
2026-10-07 12:03 ` [PATCH v3 2/7] regcache: extract __regcache_sync() to deduplicate sync dispatch Peng Fan (OSS)
2026-10-07 12:03 ` [PATCH v3 3/7] regcache: simplify control flow and reduce nesting Peng Fan (OSS)
2026-10-07 12:04 ` [PATCH v3 4/7] regmap: use krealloc_array() in regmap_register_patch() Peng Fan (OSS)
2026-10-07 12:04 ` [PATCH v3 5/7] regmap: fix potential double-free of map->reg_defaults on cache reinit Peng Fan (OSS)
2026-10-07 12:04 ` [PATCH v3 6/7] regmap: debugfs: Use __free(kfree) in regmap_name_read_file() Peng Fan (OSS)
2026-10-07 12:04 ` [PATCH v3 7/7] regmap: debugfs: Use guard to simplify code Peng Fan (OSS)
2026-10-07 13:23 ` Mark Brown [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=asZHudwIW5QkdhCg@sirena.co.uk \
--to=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=rafael@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
all inboxes | Powered by JetHome®