From: michael@ozlabs.org (Michael Ellerman)
To: <linuxppc-dev@ozlabs.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH 4/4] powerpc/pci: Properly initialize IO workaround "private"
Date: Tue, 12 Apr 2011 17:25:02 +1000 (EST) [thread overview]
Message-ID: <a586cd660c12ce1ec05fc9e8f83b765a75aaf96d.1302593231.git.michael@ellerman.id.au> (raw)
In-Reply-To: <a19ba86ac6fd999e3482e2c04b6fb10af04bb4a4.1302593231.git.michael@ellerman.id.au>
Even when no initfunc is provided.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
---
arch/powerpc/kernel/io-workarounds.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/kernel/io-workarounds.c b/arch/powerpc/kernel/io-workarounds.c
index d36515e..ffafaea 100644
--- a/arch/powerpc/kernel/io-workarounds.c
+++ b/arch/powerpc/kernel/io-workarounds.c
@@ -175,6 +175,7 @@ void __devinit iowa_register_bus(struct pci_controller *phb,
bus = &iowa_busses[iowa_bus_count];
bus->phb = phb;
bus->ops = ops;
+ bus->private = data;
if (initfunc)
if ((*initfunc)(bus, data))
--
1.7.1
next prev parent reply other threads:[~2011-04-12 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 7:25 [PATCH 1/4] powerpc/pci: Split IO vs MMIO indirect access hooks Michael Ellerman
2011-04-12 7:25 ` [PATCH 2/4] powerpc/pci: Move IO workarounds to the common kernel dir Michael Ellerman
2011-04-21 0:50 ` Benjamin Herrenschmidt
2011-04-12 7:25 ` Michael Ellerman [this message]
2011-04-12 7:25 ` [PATCH 3/4] powerpc/pci: Make IO workarounds init implicit when first bus is registered Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2011-04-11 5:54 [PATCH 1/4] powerpc/pci: Split IO vs MMIO indirect access hooks Benjamin Herrenschmidt
2011-04-11 5:54 ` [PATCH 4/4] powerpc/pci: Properly initialize IO workaround "private" Benjamin Herrenschmidt
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=a586cd660c12ce1ec05fc9e8f83b765a75aaf96d.1302593231.git.michael@ellerman.id.au \
--to=michael@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).