public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	frankja@linux.ibm.com, thuth@redhat.com, farman@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v2 0/3] Misc maintenance fixes 2022-04
Date: Thu, 21 Apr 2022 11:04:48 +0200	[thread overview]
Message-ID: <20220421110448.66af219d@p-imbrenda> (raw)
In-Reply-To: <20220421085021.1651688-1-nrb@linux.ibm.com>

On Thu, 21 Apr 2022 10:50:18 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:

> Changelog from v1:
> ----
> * tprot: Change system include to lib include in commit message
> 
> Misc small fixes, which I previously sent as:
> - [kvm-unit-tests PATCH v1 1/3] s390x: epsw: fix report_pop_prefix() when
>   running under non-QEMU
> - [kvm-unit-tests PATCH v1 2/3] s390x: tprot: use system include for mmu.h
> - [kvm-unit-tests PATCH v1 3/3] s390x: smp: make stop stopped cpu look the same
>   as the running case
> 
> I broke the threading when I sent the patches, so Janosch asked me to
> resend this as a new series.

thanks, queued

> 
> Nico Boehr (3):
>   s390x: epsw: fix report_pop_prefix() when running under non-QEMU
>   s390x: tprot: use lib include for mmu.h
>   s390x: smp: make stop stopped cpu look the same as the running case
> 
>  s390x/epsw.c  | 4 ++--
>  s390x/smp.c   | 5 +++--
>  s390x/tprot.c | 2 +-
>  3 files changed, 6 insertions(+), 5 deletions(-)
> 


      parent reply	other threads:[~2022-04-21  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  8:50 [kvm-unit-tests PATCH v2 0/3] Misc maintenance fixes 2022-04 Nico Boehr
2022-04-21  8:50 ` [kvm-unit-tests PATCH v2 1/3] s390x: epsw: fix report_pop_prefix() when running under non-QEMU Nico Boehr
2022-04-21  8:50 ` [kvm-unit-tests PATCH v2 2/3] s390x: tprot: use lib include for mmu.h Nico Boehr
2022-04-21  8:50 ` [kvm-unit-tests PATCH v2 3/3] s390x: smp: make stop stopped cpu look the same as the running case Nico Boehr
2022-04-21  9:04 ` Claudio Imbrenda [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=20220421110448.66af219d@p-imbrenda \
    --to=imbrenda@linux.ibm.com \
    --cc=farman@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=thuth@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox