From: Andrew Jones <ajones@ventanamicro.com>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
virtualization@lists.linux.dev, x86@kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Ajay Kaher <ajay.kaher@broadcom.com>,
Alexey Makhalov <alexey.makhalov@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>
Subject: Re: [PATCH v2 10/21] riscv/paravirt: Use common code for paravirt_steal_clock()
Date: Wed, 24 Sep 2025 12:08:46 -0500 [thread overview]
Message-ID: <20250924-8189d2caf8323e5f6770f429@orel> (raw)
In-Reply-To: <20250917145220.31064-11-jgross@suse.com>
On Wed, Sep 17, 2025 at 04:52:09PM +0200, Juergen Gross wrote:
> Remove the arch specific variant of paravirt_steal_clock() and use
> the common one instead.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> arch/riscv/Kconfig | 1 +
> arch/riscv/include/asm/paravirt.h | 10 ----------
> arch/riscv/kernel/paravirt.c | 7 -------
> 3 files changed, 1 insertion(+), 17 deletions(-)
>
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-09-24 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 14:51 [PATCH v2 00/21] paravirt: cleanup and reorg Juergen Gross
2025-09-17 14:52 ` [PATCH v2 05/21] paravirt: Remove asm/paravirt_api_clock.h Juergen Gross
2025-09-17 14:52 ` [PATCH v2 06/21] sched: Move clock related paravirt code to kernel/sched Juergen Gross
2025-09-17 14:52 ` [PATCH v2 10/21] riscv/paravirt: Use common code for paravirt_steal_clock() Juergen Gross
2025-09-24 17:08 ` Andrew Jones [this message]
2026-02-20 4:10 ` [PATCH v2 00/21] paravirt: cleanup and reorg patchwork-bot+linux-riscv
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=20250924-8189d2caf8323e5f6770f429@orel \
--to=ajones@ventanamicro.com \
--cc=ajay.kaher@broadcom.com \
--cc=alex@ghiti.fr \
--cc=alexey.makhalov@broadcom.com \
--cc=aou@eecs.berkeley.edu \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=virtualization@lists.linux.dev \
--cc=x86@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