[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [XEN PATCH v2] x86/APIC: address violation of MISRA C Rule 21.2
From: Nicola Vetrini <nicola.vetrini@xxxxxxxxxxx> The rule disallows the usage of an identifier reserved by the C standard. All identfiers starting with '__' are reserved for any use, so the label can be renamed in order to avoid the violation. No functional change. Signed-off-by: Nicola Vetrini <nicola.vetrini@xxxxxxxxxxx> Signed-off-by: Alessandro Zucchelli <alessandro.zucchelli@xxxxxxxxxxx> --- Changes in v2: - added correct signature - applied proper indentation for label `next' xen/arch/x86/apic.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xen/arch/x86/apic.c b/xen/arch/x86/apic.c index e077bf7edc..254ab5d388 100644 --- a/xen/arch/x86/apic.c +++ b/xen/arch/x86/apic.c @@ -925,7 +925,7 @@ void __init init_apic_mappings(void) unsigned long apic_phys; if ( x2apic_enabled ) - goto __next; + goto next; /* * If no local APIC can be found then set up a fake all * zeroes page to simulate the local APIC and another @@ -941,7 +941,7 @@ void __init init_apic_mappings(void) apic_printk(APIC_VERBOSE, "mapped APIC to %p (%08lx)\n", fix_to_virt(FIX_APIC_BASE), apic_phys); -__next: + next: /* * Fetch the APIC ID of the BSP in case we have a * default configuration (or the MP table is broken). -- 2.34.1
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |