From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964890AbcHJSxT (ORCPT ); Wed, 10 Aug 2016 14:53:19 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:36477 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964870AbcHJSxP (ORCPT ); Wed, 10 Aug 2016 14:53:15 -0400 Date: Wed, 10 Aug 2016 14:53:33 +0200 From: Ingo Molnar To: Baoquan He Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , Len Brown , Pavel Machek , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH 2/2] x86, ACPI: Fix the wrong assignment when Handle apic/x2apic entries Message-ID: <20160810125333.GB9028@gmail.com> References: <1470697311-1292-1-git-send-email-bhe@redhat.com> <1470697311-1292-2-git-send-email-bhe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1470697311-1292-2-git-send-email-bhe@redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Baoquan He wrote: > It won't impact the result, we still should fix the code bug. > > Signed-off-by: Baoquan He > Cc: "Rafael J. Wysocki" > Cc: Len Brown > Cc: Pavel Machek > Cc: Thomas Gleixner > Cc: Ingo Molnar > Cc: "H. Peter Anvin" > Cc: x86@kernel.org > Cc: linux-pm@vger.kernel.org > --- > arch/x86/kernel/acpi/boot.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c > index 90d84c3..2b25d3f 100644 > --- a/arch/x86/kernel/acpi/boot.c > +++ b/arch/x86/kernel/acpi/boot.c > @@ -1031,8 +1031,8 @@ static int __init acpi_parse_madt_lapic_entries(void) > return ret; > } > > - x2count = madt_proc[0].count; > - count = madt_proc[1].count; > + count = madt_proc[0].count; > + x2count = madt_proc[1].count; > } > if (!count && !x2count) { > printk(KERN_ERR PREFIX "No LAPIC entries present\n"); Why does this bug have no effect? Thanks, Ingo