From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Borislav Petkov <bp@amd64.org>
Cc: tony.luck@intel.com, andi@firstfloor.org,
gong.chen@linux.intel.com, ananth@in.ibm.com,
masbock@linux.vnet.ibm.com, x86@kernel.org,
linux-kernel@vger.kernel.org, lcm@us.ibm.com, mingo@redhat.com,
tglx@linutronix.de, linux-edac@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/mce: Pack boolean MCE boot flags into a structure
Date: Mon, 27 Aug 2012 21:31:11 +0530 [thread overview]
Message-ID: <503B99C7.3000503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120827154741.GI27979@aftab.osrc.amd.com>
On 08/27/2012 09:17 PM, Borislav Petkov wrote:
> On Mon, Aug 27, 2012 at 09:05:46PM +0530, Naveen N. Rao wrote:
>>>> +
>>>> +extern struct mce_boot_flags mce_boot_flags;
>>>
>>> Why do we need that extern thing?
>>
>> So that this is visible across mce.c and mce_intel.c?
>
> Ok. But if you move the struct to mce-internal.h and since both .c files
> include it, we shouldn't need that extern, right?
I'm not sure I understand. I think we still need it. This is not about
the structure, but the variable itself. extern allows mce_boot_flags
_variable_ accessible from mce_intel.c.
Thanks,
Naveen
>
> I think that'll be the most optimal placement for now.
>
> Thanks.
>
next prev parent reply other threads:[~2012-08-27 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 11:25 [PATCH 1/2] x86/mce: Pack boolean MCE boot flags into a structure Naveen N. Rao
2012-08-27 11:25 ` [PATCH 2/2] x86/mce: Honour bios-set CMCI threshold Naveen N. Rao
2012-08-27 14:48 ` Borislav Petkov
2012-08-27 15:11 ` Naveen N. Rao
2012-08-27 15:21 ` Borislav Petkov
2012-08-27 13:58 ` [PATCH 1/2] x86/mce: Pack boolean MCE boot flags into a structure Andi Kleen
2012-08-27 14:18 ` Borislav Petkov
2012-08-28 6:55 ` Naveen N. Rao
2012-08-27 14:36 ` Borislav Petkov
2012-08-27 15:35 ` Naveen N. Rao
2012-08-27 15:47 ` Borislav Petkov
2012-08-27 16:01 ` Naveen N. Rao [this message]
2012-08-27 16:34 ` Borislav Petkov
2012-08-27 17:14 ` Naveen N. Rao
2012-08-27 20:18 ` Borislav Petkov
2012-08-28 7:17 ` Naveen N. Rao
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=503B99C7.3000503@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=bp@amd64.org \
--cc=gong.chen@linux.intel.com \
--cc=lcm@us.ibm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masbock@linux.vnet.ibm.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.