From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Oleksij Rempel <o.rempel@pengutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v1 3/3] regcache: Move HW readback after cache initialisation
Date: Sun, 22 Feb 2026 23:53:32 +0000 [thread overview]
Message-ID: <6f608d0d-57fe-4e0c-aff3-540c82c00a0f@sirena.org.uk> (raw)
In-Reply-To: <20260210161058.53093-4-andriy.shevchenko@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
On Tue, Feb 10, 2026 at 05:09:10PM +0100, Andy Shevchenko wrote:
> Make sure that cache is initialised before calling any IO
> using regmap, this makes sure that we won't access NULL or
> invalid pointers in the cache which hasn't been initialised.
This doesn't apply against current code, please check and resend.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-02-22 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 16:09 [PATCH v1 0/3] regcache: Avoid accessing non-initialised cache Andy Shevchenko
2026-02-10 16:09 ` [PATCH v1 1/3] regcache: Remove duplicate check in regcache_hw_init() Andy Shevchenko
2026-02-10 16:09 ` [PATCH v1 2/3] regcache: Split regcache_count_cacheable_registers() helper Andy Shevchenko
2026-02-10 16:09 ` [PATCH v1 3/3] regcache: Move HW readback after cache initialisation Andy Shevchenko
2026-02-22 23:53 ` Mark Brown [this message]
2026-02-25 19:07 ` [PATCH v1 0/3] regcache: Avoid accessing non-initialised cache Mark Brown
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=6f608d0d-57fe-4e0c-aff3-540c82c00a0f@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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®