Xen-Devel Archive mirror
 help / color / mirror / Atom feed
From: Tamas K Lengyel <tamas@tklengyel.com>
To: Oleksii Kurochko <oleksii.kurochko@gmail.com>
Cc: xen-devel@lists.xenproject.org,
	Alexandru Isaila <aisaila@bitdefender.com>,
	 Petre Pircalabu <ppircalabu@bitdefender.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	 Bob Eshleman <bobbyeshleman@gmail.com>,
	Connor Davis <connojdavis@gmail.com>
Subject: Re: [PATCH v10 07/14] xen/riscv: introduce monitor.h
Date: Fri, 17 May 2024 21:11:14 -0400	[thread overview]
Message-ID: <CABfawh=o0pUSYACUzH4-De2mDm5_vm7Hbf5bEt6Vo8+zyU2L0A@mail.gmail.com> (raw)
In-Reply-To: <bb75ebc8bd75318759b450d398294eee8ed3ca55.1715952103.git.oleksii.kurochko@gmail.com>

On Fri, May 17, 2024 at 9:55 AM Oleksii Kurochko
<oleksii.kurochko@gmail.com> wrote:
>
> Signed-off-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>

Acked-by: Tamas K Lengyel <tamas@tklengyel.com>


  reply	other threads:[~2024-05-18  1:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 13:54 [PATCH v10 00/14] Enable build of full Xen for RISC-V Oleksii Kurochko
2024-05-17 13:54 ` [PATCH v10 01/14] xen/riscv: disable unnecessary configs Oleksii Kurochko
2024-05-17 13:54 ` [PATCH v10 02/14] xen: introduce generic non-atomic test_*bit() Oleksii Kurochko
2024-05-21 11:10   ` Jan Beulich
2024-05-23 13:00   ` Julien Grall
2024-05-23 14:11     ` Oleksii K.
2024-05-23 14:33       ` Julien Grall
2024-05-23 16:40         ` Oleksii K.
2024-05-24  6:48           ` Jan Beulich
2024-05-24  7:25             ` Oleksii K.
2024-05-24  7:35               ` Jan Beulich
2024-05-24  8:06                 ` Oleksii K.
2024-05-24  8:58         ` Oleksii K.
2024-05-24  9:17           ` Julien Grall
2024-05-17 13:54 ` [PATCH v10 03/14] xen/bitops: implement fls{l}() in common logic Oleksii Kurochko
2024-05-21 11:18   ` Jan Beulich
2024-05-22  7:37     ` Oleksii K.
2024-05-22  8:15       ` Jan Beulich
2024-05-23 13:21         ` Julien Grall
2024-05-17 13:54 ` [PATCH v10 04/14] xen/riscv: introduce bitops.h Oleksii Kurochko
2024-05-17 13:54 ` [PATCH v10 05/14] xen/riscv: introduce cmpxchg.h Oleksii Kurochko
2024-05-17 13:54 ` [PATCH v10 06/14] xen/riscv: introduce atomic.h Oleksii Kurochko
2024-05-17 13:54 ` [PATCH v10 07/14] xen/riscv: introduce monitor.h Oleksii Kurochko
2024-05-18  1:11   ` Tamas K Lengyel [this message]
2024-05-17 13:54 ` [PATCH v10 08/14] xen/riscv: add definition of __read_mostly Oleksii Kurochko
2024-05-17 13:54 ` [PATCH v10 09/14] xen/riscv: add required things to current.h Oleksii Kurochko
2024-05-17 13:54 ` [PATCH v10 10/14] xen/riscv: add minimal stuff to mm.h to build full Xen Oleksii Kurochko
2024-05-17 13:55 ` [PATCH v10 11/14] xen/riscv: introduce vm_event_*() functions Oleksii Kurochko
2024-05-18  1:12   ` Tamas K Lengyel
2024-05-17 13:55 ` [PATCH v10 12/14] xen/riscv: add minimal amount of stubs to build full Xen Oleksii Kurochko
2024-05-17 13:55 ` [PATCH v10 13/14] xen/riscv: enable full Xen build Oleksii Kurochko
2024-05-17 13:55 ` [PATCH v10 14/14] xen/README: add compiler and binutils versions for RISC-V64 Oleksii Kurochko

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='CABfawh=o0pUSYACUzH4-De2mDm5_vm7Hbf5bEt6Vo8+zyU2L0A@mail.gmail.com' \
    --to=tamas@tklengyel.com \
    --cc=aisaila@bitdefender.com \
    --cc=alistair.francis@wdc.com \
    --cc=bobbyeshleman@gmail.com \
    --cc=connojdavis@gmail.com \
    --cc=oleksii.kurochko@gmail.com \
    --cc=ppircalabu@bitdefender.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).