From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>, "Glauber Costa" <glommer@gmail.com>
Cc: "Linux Kernel ML" <linux-kernel@vger.kernel.org>
Subject: [PATCH] x86: change pci_direct_conf1 back not static
Date: Tue, 18 Mar 2008 11:02:39 -0700 [thread overview]
Message-ID: <86802c440803181102i5175c12cw7c41b3f68de38f04@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: pci_direct_conf1.patch --]
[-- Type: text/x-patch; name=pci_direct_conf1.patch, Size: 1137 bytes --]
[PATCH] x86: change pci_direct_conf1 back not static
Glauber Costa <glommer@gmail.com> pointed out
commit 513f484dfe5cbb53e73ef1729703e7030e799487
x86 pci: remove checking type for mmconfig probe v2
broke the VISW.
remove the static in declaration.
Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
diff --git a/arch/x86/pci/direct.c b/arch/x86/pci/direct.c
index 739ce26..21d1e0e 100644
--- a/arch/x86/pci/direct.c
+++ b/arch/x86/pci/direct.c
@@ -76,7 +76,7 @@ static int pci_conf1_write(unsigned int seg, unsigned int bus,
#undef PCI_CONF1_ADDRESS
-static struct pci_raw_ops pci_direct_conf1 = {
+struct pci_raw_ops pci_direct_conf1 = {
.read = pci_conf1_read,
.write = pci_conf1_write,
};
diff --git a/arch/x86/pci/pci.h b/arch/x86/pci/pci.h
index d345661..c9fb637 100644
--- a/arch/x86/pci/pci.h
+++ b/arch/x86/pci/pci.h
@@ -95,6 +95,8 @@ struct pci_raw_ops {
extern struct pci_raw_ops *raw_pci_ops;
extern struct pci_raw_ops *raw_pci_ext_ops;
+extern struct pci_raw_ops pci_direct_conf1;
+
extern int pci_direct_probe(void);
extern void pci_direct_init(int type);
extern void pci_pcbios_init(void);
next reply other threads:[~2008-03-19 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 18:02 Yinghai Lu [this message]
2008-03-21 11:26 ` Ingo Molnar
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=86802c440803181102i5175c12cw7c41b3f68de38f04@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®