Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964810AbaLKQ50 (ORCPT ); Thu, 11 Dec 2014 11:57:26 -0500 Received: from mail-ie0-f179.google.com ([209.85.223.179]:36498 "EHLO mail-ie0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933615AbaLKQ5Z (ORCPT ); Thu, 11 Dec 2014 11:57:25 -0500 MIME-Version: 1.0 In-Reply-To: References: <1414387308-27148-5-git-send-email-jiang.liu@linux.intel.com> Date: Thu, 11 Dec 2014 08:57:24 -0800 X-Google-Sender-Auth: adtnYP1JJ2w964j8J7n6zVABXiw Message-ID: Subject: Re: [tip:x86/apic] x86, PCI, ACPI: Kill private function resource_to_addr() in arch/x86/pci/acpi.c From: Yinghai Lu To: Thomas Gleixner Cc: Jiang Liu , "H. Peter Anvin" , Bjorn Helgaas , "Rafael J. Wysocki" , Borislav Petkov , Randy Dunlap , Ingo Molnar , Joerg Roedel , Tony Luck , Konrad Rzeszutek Wilk , Greg Kroah-Hartman , Benjamin Herrenschmidt , Linux Kernel Mailing List , Linus Torvalds , "linux-tip-commits@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 11, 2014 at 8:36 AM, Thomas Gleixner wrote: > On Wed, 10 Dec 2014, Yinghai Lu wrote: >> On Wed, Dec 10, 2014 at 12:15 PM, Thomas Gleixner wrote: >> >> - struct resource r = { >> >> - .flags = 0 >> >> - }; >> >> + struct resource r; >> >> >> >> + memset(&r, 0, sizeof(r)); >> > >> > What's the point of this change? Both initialize r to 0. memset() >> > generates better code, but that's irrelevant for the problem at hand. > > Did you actually read what I wrote? > > struct resource r = { > .flags = 0 > }; > > initializes r completely to 0. So how do you get a random pointer in r? ok, I get it now. I was thinking that compiler will generate code like struct resource r; r.flags = 0; Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/