From: Tim Chen <tim.c.chen@linux.intel.com>
To: Davi Chaves Azevedo <davichazbh@gmail.com>, kprateek.nayak@amd.com
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Chen Yu <yu.c.chen@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Valentin Schneider <vschneid@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
chen.yu@linux.dev, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched/cache: Refresh LLC capacity across CPU hotplug
Date: Tue, 15 Sep 2026 13:34:28 -0700 [thread overview]
Message-ID: <7aed4a31e3608c0b7edae57edcb245c912ce5f92.camel@linux.intel.com> (raw)
In-Reply-To: <20260915175714.2015751-1-davichazbh@gmail.com>
On Tue, 2026-09-15 at 14:57 -0300, Davi Chaves Azevedo wrote:
> Hi Prateek,
>
> Thanks for the review and testing. I've added both tags to my local patch,
> with no code changes.
>
> Tim, may I include your Reviewed-by?
>
Yes, you can add my Reviewed-by.
Tim
> Chenyu, may I include your Tested-by
> for the Ryzen and Xeon checks you reported too?
>
> Thanks,
> Davi
next prev parent reply other threads:[~2026-09-15 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 13:48 [PATCH] sched/cache: Refresh LLC capacity across CPU hotplug Davi Chaves Azevedo
2026-09-11 18:24 ` Chen, Yu C
2026-09-11 22:10 ` Davi Chaves Azevedo
2026-09-11 22:02 ` [PATCH v2] " Davi Chaves Azevedo
2026-09-12 0:55 ` Tim Chen
2026-09-15 16:08 ` K Prateek Nayak
2026-09-15 17:57 ` Davi Chaves Azevedo
2026-09-15 20:34 ` Tim Chen [this message]
2026-09-16 1:34 ` Chen, Yu C
2026-09-16 13:44 ` [PATCH v3] " Davi Chaves Azevedo
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=7aed4a31e3608c0b7edae57edcb245c912ce5f92.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=chen.yu@linux.dev \
--cc=dakr@kernel.org \
--cc=davichazbh@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yu.c.chen@intel.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.