From: Oliver Upton <oliver.upton@linux.dev>
To: Oliver Upton <oliver.upton@linux.dev>, kvmarm@lists.linux.dev
Cc: Aishwarya TCV <aishwarya.tcv@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
James Morse <james.morse@arm.com>,
kvm@vger.kernel.org, Nina Schoetterl-Glausch <nsg@linux.ibm.com>,
Marc Zyngier <maz@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [PATCH 0/2] tools: Makefile fixes for sysreg generation
Date: Tue, 31 Oct 2023 00:19:19 +0000 [thread overview]
Message-ID: <169871155376.54520.13627627149376112404.b4-ty@linux.dev> (raw)
In-Reply-To: <20231027005439.3142015-1-oliver.upton@linux.dev>
On Fri, 27 Oct 2023 00:54:37 +0000, Oliver Upton wrote:
> Fixing a couple of issues in the Makefile changes required to get sysreg
> generation working.
>
> Cc: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> Cc: Aishwarya TCV <aishwarya.tcv@arm.com>
>
> Oliver Upton (2):
> tools: arm64: Fix references to top srcdir in Makefile
> KVM: selftests: Avoid using forced target for generating arm64 headers
>
> [...]
Applied to kvmarm/next, thanks!
[1/2] tools headers arm64: Fix references to top srcdir in Makefile
https://git.kernel.org/kvmarm/kvmarm/c/fbb075c11663
[2/2] KVM: selftests: Avoid using forced target for generating arm64 headers
https://git.kernel.org/kvmarm/kvmarm/c/70c7b704ca72
--
Best,
Oliver
prev parent reply other threads:[~2023-10-31 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 0:54 [PATCH 0/2] tools: Makefile fixes for sysreg generation Oliver Upton
2023-10-27 0:54 ` [PATCH 1/2] tools headers arm64: Fix references to top srcdir in Makefile Oliver Upton
2023-10-27 0:54 ` [PATCH 2/2] KVM: selftests: Avoid using forced target for generating arm64 headers Oliver Upton
2023-10-30 16:34 ` Nina Schoetterl-Glausch
2023-10-31 0:19 ` Oliver Upton [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=169871155376.54520.13627627149376112404.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=aishwarya.tcv@arm.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=nsg@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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