public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v1 0/4] regcache: Split out ->populate()
Date: Thu, 30 Oct 2025 13:43:17 +0200	[thread overview]
Message-ID: <aQNPVUSKeg9odlRF@smile.fi.intel.com> (raw)
In-Reply-To: <c33c5930-ad6e-4ff0-9a6f-4dfd15fcd352@sirena.org.uk>

On Thu, Oct 30, 2025 at 11:36:27AM +0000, Mark Brown wrote:
> On Wed, Oct 29, 2025 at 08:28:57AM +0100, Andy Shevchenko wrote:
> > This is a refactoring series to decouple cache initialisation and population.
> > On its own it has no functional impact but will be used in the further
> > development. Besides that I found this split useful on its own (from the design
> > perspective). That's why I decided to send it out as is separately from a bigger
> > (and ongoing) work.
> 
> This looks fine but needs a rebase onto the latest code.

Will do, thanks!

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2025-10-30 11:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29  7:28 [PATCH v1 0/4] regcache: Split out ->populate() Andy Shevchenko
2025-10-29  7:28 ` [PATCH v1 1/4] regcache: Add ->populate() callback to separate from ->init() Andy Shevchenko
2025-10-29  7:28 ` [PATCH v1 2/4] regcache: rbtree: Split ->populate() " Andy Shevchenko
2025-10-29  7:29 ` [PATCH v1 3/4] regcache: flat: " Andy Shevchenko
2025-10-29  7:29 ` [PATCH v1 4/4] regcache: maple: " Andy Shevchenko
2025-10-30 11:36 ` [PATCH v1 0/4] regcache: Split out ->populate() Mark Brown
2025-10-30 11:43   ` Andy Shevchenko [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=aQNPVUSKeg9odlRF@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dakr@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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