From: Steffen Eiden <seiden@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: frankja@linux.ibm.com, thuth@redhat.com, david@redhat.com,
nrb@linux.ibm.com, scgl@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v2 5/6] s390x: skrf: use CPU indexes instead of addresses
Date: Tue, 15 Feb 2022 12:26:55 +0100 [thread overview]
Message-ID: <41a6f895-c8bf-e82c-24c1-e69ca406a853@linux.ibm.com> (raw)
In-Reply-To: <20220204130855.39520-6-imbrenda@linux.ibm.com>
On 2/4/22 14:08, Claudio Imbrenda wrote:
> Adapt the test to the new semantics of the smp_* functions, and use CPU
> indexes instead of addresses.
>
> Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
next prev parent reply other threads:[~2022-02-15 11:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:08 [kvm-unit-tests PATCH v2 0/6] s390x: smp: use CPU indexes instead of addresses Claudio Imbrenda
2022-02-04 13:08 ` [kvm-unit-tests PATCH v2 1/6] lib: s390x: smp: guarantee that boot CPU has index 0 Claudio Imbrenda
2022-02-14 16:05 ` Nico Boehr
2022-02-15 10:46 ` Steffen Eiden
2022-02-04 13:08 ` [kvm-unit-tests PATCH v2 2/6] lib: s390x: smp: refactor smp functions to accept indexes Claudio Imbrenda
2022-02-14 16:05 ` Nico Boehr
2022-02-15 11:09 ` Steffen Eiden
2022-02-15 11:23 ` Claudio Imbrenda
2022-02-15 11:43 ` Steffen Eiden
2022-02-15 11:54 ` Claudio Imbrenda
2022-02-15 15:11 ` Janosch Frank
2022-02-04 13:08 ` [kvm-unit-tests PATCH v2 3/6] s390x: smp: use CPU indexes instead of addresses Claudio Imbrenda
2022-02-14 16:06 ` Nico Boehr
2022-02-15 11:15 ` Steffen Eiden
2022-02-04 13:08 ` [kvm-unit-tests PATCH v2 4/6] s390x: firq: " Claudio Imbrenda
2022-02-14 16:06 ` Nico Boehr
2022-02-15 11:23 ` Steffen Eiden
2022-02-04 13:08 ` [kvm-unit-tests PATCH v2 5/6] s390x: skrf: " Claudio Imbrenda
2022-02-14 16:06 ` Nico Boehr
2022-02-15 11:26 ` Steffen Eiden [this message]
2022-02-04 13:08 ` [kvm-unit-tests PATCH v2 6/6] s390x: uv-host: " Claudio Imbrenda
2022-02-14 16:11 ` Nico Boehr
2022-02-15 11:31 ` Steffen Eiden
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=41a6f895-c8bf-e82c-24c1-e69ca406a853@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=scgl@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 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.