public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel•org>
To: Paolo Bonzini <pbonzini@redhat•com>
Cc: Mark Rutland <mark.rutland@arm•com>,
	Andrew Jones <drjones@redhat•com>,
	kvm@vger•kernel.org, Fangrui Song <maskray@google•com>,
	Suzuki K Poulose <suzuki.poulose@arm•com>,
	Nick Desaulniers <ndesaulniers@google•com>,
	James Morse <james.morse@arm•com>,
	linux-arm-kernel@lists•infradead.org,
	Zenghui Yu <yuzenghui@huawei•com>, Will Deacon <will@kernel•org>,
	kvmarm@lists•cs.columbia.edu,
	Julien Thierry <julien.thierry.kdev@gmail•com>
Subject: [PATCH 1/4] KVM: arm64: Delete duplicated label in invalid_vector
Date: Fri,  1 May 2020 11:12:01 +0100	[thread overview]
Message-ID: <20200501101204.364798-2-maz@kernel.org> (raw)
In-Reply-To: <20200501101204.364798-1-maz@kernel.org>

From: Fangrui Song <maskray@google•com>

SYM_CODE_START defines \label , so it is redundant to define \label again.
A redefinition at the same place is accepted by GNU as
(https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=159fbb6088f17a341bcaaac960623cab881b4981)
but rejected by the clang integrated assembler.

Fixes: 617a2f392c92 ("arm64: kvm: Annotate assembly using modern annoations")
Signed-off-by: Fangrui Song <maskray@google•com>
Signed-off-by: Marc Zyngier <maz@kernel•org>
Tested-by: Nick Desaulniers <ndesaulniers@google•com>
Reviewed-by: Nick Desaulniers <ndesaulniers@google•com>
Link: https://github.com/ClangBuiltLinux/linux/issues/988
Link: https://lore.kernel.org/r/20200413231016.250737-1-maskray@google.com
---
 arch/arm64/kvm/hyp/hyp-entry.S | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/arm64/kvm/hyp/hyp-entry.S b/arch/arm64/kvm/hyp/hyp-entry.S
index c2a13ab3c471..9c5cfb04170e 100644
--- a/arch/arm64/kvm/hyp/hyp-entry.S
+++ b/arch/arm64/kvm/hyp/hyp-entry.S
@@ -198,7 +198,6 @@ SYM_CODE_END(__hyp_panic)
 .macro invalid_vector	label, target = __hyp_panic
 	.align	2
 SYM_CODE_START(\label)
-\label:
 	b \target
 SYM_CODE_END(\label)
 .endm
-- 
2.26.2


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-05-01 10:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 10:12 [GIT PULL] KVM/arm fixes for 5.7, take #2 Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier [this message]
2020-05-01 10:12 ` [PATCH 2/4] KVM: arm64: Save/restore sp_el0 as part of __guest_enter Marc Zyngier
2020-05-01 10:12 ` [PATCH 3/4] KVM: arm64: vgic-v4: Initialize GICv4.1 even in the absence of a virtual ITS Marc Zyngier
2020-05-01 10:12 ` [PATCH 4/4] KVM: arm64: Fix 32bit PC wrap-around Marc Zyngier
2020-05-04 11:30 ` [GIT PULL] KVM/arm fixes for 5.7, take #2 Will Deacon
2020-05-04 16:05   ` Paolo Bonzini
2020-05-04 16:51     ` Will Deacon
2020-05-04 17:02       ` Paolo Bonzini

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=20200501101204.364798-2-maz@kernel.org \
    --to=maz@kernel$(echo .)org \
    --cc=drjones@redhat$(echo .)com \
    --cc=james.morse@arm$(echo .)com \
    --cc=julien.thierry.kdev@gmail$(echo .)com \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=kvmarm@lists$(echo .)cs.columbia.edu \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=maskray@google$(echo .)com \
    --cc=ndesaulniers@google$(echo .)com \
    --cc=pbonzini@redhat$(echo .)com \
    --cc=suzuki.poulose@arm$(echo .)com \
    --cc=will@kernel$(echo .)org \
    --cc=yuzenghui@huawei$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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