From: Chen Gang <gang.chen@asianux•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>,
"paulus@samba•org" <paulus@samba•org>,
shangw@linux•vnet.ibm.com, weiyang@linux•vnet.ibm.com,
linuxram@us•ibm.com, Bjorn Helgaas <bhelgaas@google•com>
Cc: "linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>
Subject: [PATCH] powerpc: platforms: powernv: add '__init' for pnv_pci_init_ioda2_phb()
Date: Mon, 22 Jul 2013 14:52:20 +0800 [thread overview]
Message-ID: <51ECD6A4.3050408@asianux.com> (raw)
pnv_pci_init_ioda2_phb() is only used during boot up, so need add
'__init' to save the related memory, and avoid related warning:
The function .pnv_pci_init_ioda2_phb() references
the function __init .pnv_pci_init_ioda_phb().
This is often because .pnv_pci_init_ioda2_phb lacks a __init
annotation or the annotation of .pnv_pci_init_ioda_phb is wrong.
Signed-off-by: Chen Gang <gang.chen@asianux•com>
---
arch/powerpc/platforms/powernv/pci-ioda.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/pci-ioda.c b/arch/powerpc/platforms/powernv/pci-ioda.c
index 49b57b9..d8140b1 100644
--- a/arch/powerpc/platforms/powernv/pci-ioda.c
+++ b/arch/powerpc/platforms/powernv/pci-ioda.c
@@ -1266,7 +1266,7 @@ void __init pnv_pci_init_ioda_phb(struct device_node *np,
opal_pci_set_pe(phb_id, 0, 0, 7, 1, 1 , OPAL_MAP_PE);
}
-void pnv_pci_init_ioda2_phb(struct device_node *np)
+void __init pnv_pci_init_ioda2_phb(struct device_node *np)
{
pnv_pci_init_ioda_phb(np, 0, PNV_PHB_IODA2);
}
--
1.7.7.6
next reply other threads:[~2013-07-22 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 6:52 Chen Gang [this message]
2013-07-23 0:28 ` [PATCH] powerpc: platforms: powernv: add '__init' for pnv_pci_init_ioda2_phb() Bjorn Helgaas
2013-07-23 0:37 ` Chen Gang
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=51ECD6A4.3050408@asianux.com \
--to=gang.chen@asianux$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=bhelgaas@google$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=linuxram@us$(echo .)ibm.com \
--cc=paulus@samba$(echo .)org \
--cc=shangw@linux$(echo .)vnet.ibm.com \
--cc=weiyang@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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