From: Steffen Eiden <seiden@linux.ibm.com>
To: Andreas Grapentin <gra@linux.ibm.com>
Cc: Marc Zyngier <maz@kernel.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] KVM: s390: arm64: Fix kvm_arm64 module naming consistency
Date: Wed, 4 Nov 2026 09:07:36 +0100 [thread overview]
Message-ID: <20261104080736.8132-C-seiden@linux.ibm.com> (raw)
In-Reply-To: <20261103-s390_arm64_kvm_fixups-v1-3-21c36fedd878@linux.ibm.com>
On Tue, Nov 03, 2026 at 05:37:04PM +0100, Andreas Grapentin wrote:
> the module build for the kvm_arm64 module produced kvm-arm64.ko, fix the
Nit: start with an upper case T
> Makefile to produce kvm_arm64.ko instead, so the output file name
> matches the module name.
>
> Signed-off-by: Andreas Grapentin <gra@linux.ibm.com>
Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
next prev parent reply other threads:[~2026-11-04 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 16:37 [PATCH 0/3] KVM: s390: arm64: Fixes for arm64 KVM support Andreas Grapentin
2026-11-03 16:37 ` [PATCH 1/3] KVM: s390: arm64: Turn vcpu->arch.pause into a counter Andreas Grapentin
2026-11-04 8:12 ` Andreas Grapentin
2026-11-03 16:37 ` [PATCH 2/3] KVM: s390: arm64: Declare enum vcpu_sysreg Andreas Grapentin
2026-11-04 8:01 ` Steffen Eiden
2026-11-04 9:20 ` Christian Borntraeger
2026-11-03 16:37 ` [PATCH 3/3] KVM: s390: arm64: Fix kvm_arm64 module naming consistency Andreas Grapentin
2026-11-04 8:07 ` Steffen Eiden [this message]
2026-11-04 9:16 ` Christian Borntraeger
2026-11-03 18:31 ` [PATCH 0/3] KVM: s390: arm64: Fixes for arm64 KVM support Marc Zyngier
2026-11-04 7:59 ` 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=20261104080736.8132-C-seiden@linux.ibm.com \
--to=seiden@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=gra@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=maz@kernel.org \
--cc=svens@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®