From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Daniel Henrique Barboza" <danielhb413@gmail.com>, <qemu-ppc@nongnu.org>
Cc: <qemu-devel@nongnu.org>, "Harsh Prateek Bora" <harshpb@linux.ibm.com>
Subject: Re: [PATCH 4/4] ppc/spapr: Move spapr nested HV to a new file
Date: Tue, 20 Jun 2023 13:41:00 +1000 [thread overview]
Message-ID: <CTH5ZNVFOSL2.Q42839O8BVBR@wheely> (raw)
In-Reply-To: <ffe96bb1-dee9-2736-68db-85e37a65e1ae@gmail.com>
On Sun Jun 18, 2023 at 7:53 PM AEST, Daniel Henrique Barboza wrote:
> Nick,
>
> Do you plan to send a new version of this patch with a spapr_nested.h
> header included? Otherwise I'll pick this one as is.
Hey Daniel,
I'll send another series shortly with the header split out.
Thanks,
Nick
prev parent reply other threads:[~2023-06-20 3:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 9:13 [PATCH 0/4] ppc/spapr: Nested HV fix and tidying Nicholas Piggin
2023-06-08 9:13 ` [PATCH 1/4] ppc/spapr: H_ENTER_NESTED should restore host XER ca field Nicholas Piggin
2023-06-09 7:05 ` Harsh Prateek Bora
2023-06-14 11:53 ` Nicholas Piggin
2023-06-08 9:13 ` [PATCH 2/4] ppc/spapr: Add a nested state struct Nicholas Piggin
2023-06-09 7:09 ` Harsh Prateek Bora
2023-06-14 11:56 ` Nicholas Piggin
2023-06-15 4:51 ` Harsh Prateek Bora
2023-06-15 5:36 ` Nicholas Piggin
2023-06-08 9:13 ` [PATCH 3/4] ppc/spapr: load and store l2 state with helper functions Nicholas Piggin
2023-06-09 8:00 ` Harsh Prateek Bora
2023-06-14 12:02 ` Nicholas Piggin
2023-06-15 4:53 ` Harsh Prateek Bora
2023-06-08 9:13 ` [PATCH 4/4] ppc/spapr: Move spapr nested HV to a new file Nicholas Piggin
2023-06-15 6:30 ` Harsh Prateek Bora
2023-06-15 11:51 ` Nicholas Piggin
2023-06-16 4:57 ` Harsh Prateek Bora
2023-06-18 9:53 ` Daniel Henrique Barboza
2023-06-20 3:41 ` Nicholas Piggin [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=CTH5ZNVFOSL2.Q42839O8BVBR@wheely \
--to=npiggin@gmail.com \
--cc=danielhb413@gmail.com \
--cc=harshpb@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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 NNTP newsgroup(s).