From: Janosch Frank <frankja@linux.ibm.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] KVM: s390: Some gaccess cleanup
Date: Tue, 23 Nov 2021 13:39:45 +0100 [thread overview]
Message-ID: <e15c57b9-f52d-0ca9-ae77-f01fb8c8eab7@linux.ibm.com> (raw)
In-Reply-To: <20211028135556.1793063-1-scgl@linux.ibm.com>
On 10/28/21 15:55, Janis Schoetterl-Glausch wrote:
> Cleanup s390 guest access code a bit, getting rid of some code
> duplication and improving readability.
>
> v1 -> v2
> separate patch for renamed variable
> fragment_len instead of seg
> expand comment of guest_range_to_gpas
> fix nits
>
> I did not pick up Janosch's Reviewed-by because of the split patch
> and the changed variable name.
>
> Janis Schoetterl-Glausch (3):
> KVM: s390: gaccess: Refactor gpa and length calculation
> KVM: s390: gaccess: Refactor access address range check
> KVM: s390: gaccess: Cleanup access to guest frames
>
> arch/s390/kvm/gaccess.c | 158 +++++++++++++++++++++++-----------------
> 1 file changed, 92 insertions(+), 66 deletions(-)
>
Could you please push this to devel so we get some CI coverage?
prev parent reply other threads:[~2021-11-23 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 13:55 Janis Schoetterl-Glausch
2021-10-28 13:55 ` [PATCH v2 1/3] KVM: s390: gaccess: Refactor gpa and length calculation Janis Schoetterl-Glausch
2021-11-19 8:27 ` Janosch Frank
2021-11-23 12:38 ` Janosch Frank
2021-10-28 13:55 ` [PATCH v2] KVM: s390: gaccess: Refactor access address range check Janis Schoetterl-Glausch
2021-11-19 8:56 ` Janosch Frank
2021-11-19 10:01 ` Janis Schoetterl-Glausch
2021-10-28 13:55 ` [PATCH v2 3/3] KVM: s390: gaccess: Cleanup access to guest frames Janis Schoetterl-Glausch
2021-10-28 14:25 ` David Hildenbrand
2021-10-28 14:48 ` Janis Schoetterl-Glausch
2021-11-19 9:00 ` Janosch Frank
2021-11-22 11:13 ` David Hildenbrand
2021-11-23 12:39 ` Janosch Frank [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=e15c57b9-f52d-0ca9-ae77-f01fb8c8eab7@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=scgl@linux.ibm.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
all inboxes | Powered by JetHome®