From: Hanna Hawa <hhhawa@amazon.com>
To: <bp@alien8.de>, <mchehab@kernel.org>, <tony.luck@intel.com>,
<james.morse@arm.com>, <rrichter@marvell.com>,
<hhhawa@amazon.com>, <robh+dt@kernel.org>,
<frowand.list@gmail.com>, <davem@davemloft.net>,
<gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-edac@vger.kernel.org>,
<devicetree@vger.kernel.org>, <dwmw@amazon.co.uk>,
<benh@amazon.com>, <ronenk@amazon.com>, <talel@amazon.com>,
<jonnyc@amazon.com>, <hanochu@amazon.com>, <eitan@amazon.com>
Subject: [PATCH v10 2/3] of: EXPORT_SYMBOL_GPL of_find_next_cache_node
Date: Sun, 10 May 2020 18:13:09 +0300 [thread overview]
Message-ID: <20200510151310.17372-3-hhhawa@amazon.com> (raw)
In-Reply-To: <20200510151310.17372-1-hhhawa@amazon.com>
Make of_find_next_cache_node() available for modules.
Signed-off-by: Hanna Hawa <hhhawa@amazon.com>
Acked-by: Rob Herring <robh@kernel.org>
---
drivers/of/base.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/of/base.c b/drivers/of/base.c
index ae03b1218b06..1f8daf4c3398 100644
--- a/drivers/of/base.c
+++ b/drivers/of/base.c
@@ -2174,6 +2174,7 @@ struct device_node *of_find_next_cache_node(const struct device_node *np)
return NULL;
}
+EXPORT_SYMBOL_GPL(of_find_next_cache_node);
/**
* of_find_last_cache_level - Find the level at which the last cache is
--
2.17.1
next prev parent reply other threads:[~2020-05-10 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 15:13 [PATCH v10 0/3] Introduce Amazon's Annapurna Labs L1/L2 EDAC drivers Hanna Hawa
2020-05-10 15:13 ` [PATCH v10 1/3] edac: Introduce Amazon's Annapurna Labs L1 EDAC driver Hanna Hawa
2020-05-10 15:13 ` Hanna Hawa [this message]
2020-05-10 15:13 ` [PATCH v10 3/3] edac: Introduce Amazon's Annapurna Labs L2 " Hanna Hawa
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=20200510151310.17372-3-hhhawa@amazon.com \
--to=hhhawa@amazon.com \
--cc=benh@amazon.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=eitan@amazon.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=james.morse@arm.com \
--cc=jonnyc@amazon.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ronenk@amazon.com \
--cc=rrichter@marvell.com \
--cc=talel@amazon.com \
--cc=tony.luck@intel.com \
/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).