From: David Hildenbrand <david@redhat.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Cc: 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 v3 1/3] KVM: s390: gaccess: Refactor gpa and length calculation
Date: Fri, 26 Nov 2021 18:10:38 +0100 [thread overview]
Message-ID: <78b0d664-a029-b239-c7ab-cb5ce0b2d269@redhat.com> (raw)
In-Reply-To: <20211126164549.7046-2-scgl@linux.ibm.com>
On 26.11.21 17:45, Janis Schoetterl-Glausch wrote:
> Improve readability by renaming the length variable and
> not calculating the offset manually.
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> arch/s390/kvm/gaccess.c | 32 +++++++++++++++++---------------
> 1 file changed, 17 insertions(+), 15 deletions(-)
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-11-26 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 16:45 [PATCH v3 0/3] KVM: s390: Some gaccess cleanup Janis Schoetterl-Glausch
2021-11-26 16:45 ` [PATCH v3 1/3] KVM: s390: gaccess: Refactor gpa and length calculation Janis Schoetterl-Glausch
2021-11-26 17:10 ` David Hildenbrand [this message]
2021-11-29 8:55 ` Claudio Imbrenda
2021-11-26 16:45 ` [PATCH v3 2/3] KVM: s390: gaccess: Refactor access address range check Janis Schoetterl-Glausch
2021-11-29 9:13 ` Claudio Imbrenda
2021-11-26 16:45 ` [PATCH v3 3/3] KVM: s390: gaccess: Cleanup access to guest pages Janis Schoetterl-Glausch
2021-11-26 17:09 ` David Hildenbrand
2021-11-29 8:59 ` Claudio Imbrenda
2021-11-29 9:17 ` Janis Schoetterl-Glausch
2021-12-07 9:27 ` [PATCH v3 0/3] KVM: s390: Some gaccess cleanup Janosch Frank
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=78b0d664-a029-b239-c7ab-cb5ce0b2d269@redhat.com \
--to=david@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.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