From: "H. Peter Anvin" <hpa@zytor.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, Julia Lawall <julia@diku.dk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: incompatible struct pci_root_info?
Date: Sat, 14 May 2011 11:07:39 -0700 [thread overview]
Message-ID: <4DCEC4EB.2050107@zytor.com> (raw)
In-Reply-To: <4DCEB5BB.1080202@freemail.hu>
On 05/14/2011 10:02 AM, Németh Márton wrote:
>
> As far as I know it is OK to have different types on different architectures
> with the same name. Is there any reason behind having two struct pci_root_info
> delcaration in arch/x86?
>
It looks like a namespace collision; the same name being used for that
is really two different types.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2011-05-14 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 17:02 incompatible struct pci_root_info? Németh Márton
2011-05-14 18:07 ` H. Peter Anvin [this message]
2011-05-15 19:09 ` [PATCH] x86 pci acpi: rename struct pci_root_info Németh Márton
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=4DCEC4EB.2050107@zytor.com \
--to=hpa@zytor.com \
--cc=fenghua.yu@intel.com \
--cc=julia@diku.dk \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nm127@freemail.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox