From: kbuild test robot <lkp@intel.com>
To: Laura Abbott <labbott@fedoraproject.org>
Cc: kbuild-all@01.org, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Andrew Andrianov <andrew@ncrmnt.org>,
arve@android.com, Riley Andrews <riandrews@android.com>,
Laura Abbott <laura@labbott.name>,
John Stultz <john.stultz@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Tom Gall <tom.gall@linaro.org>, Colin Cross <ccross@google.com>,
devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
romlem@google.com, mitchelh@codeaurora.org,
linux-arm-kernel@lists.infradead.org,
Feng Tang <feng.tang@intel.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: [RFC PATCH] staging: ion: ion_parse_dt_heap_common() can be static
Date: Wed, 7 Oct 2015 05:29:32 +0800 [thread overview]
Message-ID: <20151006212932.GA59274@xian> (raw)
In-Reply-To: <1444164433-9107-3-git-send-email-labbott@fedoraproject.org>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
ion_of.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/android/ion/ion_of.c b/drivers/staging/android/ion/ion_of.c
index 3c9b1e5..daded0c 100644
--- a/drivers/staging/android/ion/ion_of.c
+++ b/drivers/staging/android/ion/ion_of.c
@@ -28,7 +28,7 @@
* Future work: allow callback function for each heap?
*/
-int ion_parse_dt_heap_common(struct device_node *heap_node,
+static int ion_parse_dt_heap_common(struct device_node *heap_node,
struct ion_platform_heap *heap)
{
u32 ion_heap_id, ion_heap_align, ion_heap_type;
@@ -67,7 +67,7 @@ int ion_parse_dt_heap_common(struct device_node *heap_node,
return 0;
}
-int ion_setup_heap_common(struct platform_device *parent,
+static int ion_setup_heap_common(struct platform_device *parent,
struct device_node *heap_node,
struct ion_platform_heap *heap)
{
next prev parent reply other threads:[~2015-10-06 21:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 20:47 [RFC][PATCH 0/2] Devicetree bindings for Ion Laura Abbott
2015-10-06 20:47 ` [RFC][PATCH 1/2] WIP: " Laura Abbott
2015-10-06 22:35 ` Rob Herring
2015-10-06 23:01 ` Laura Abbott
2015-10-07 10:36 ` Andrew
2015-10-07 18:36 ` Rob Herring
2015-10-07 19:23 ` Andrew
2015-10-08 1:43 ` Laura Abbott
2015-10-12 18:39 ` Mitchel Humpherys
2015-10-13 8:14 ` Andrew
2015-10-20 16:34 ` Mitchel Humpherys
2015-10-22 10:36 ` andrew
2015-10-22 17:23 ` Laura Abbott
2015-10-06 20:47 ` [RFC][PATCH 2/2] staging: ion: Add files for parsing the devicetree (WIP) Laura Abbott
2015-10-06 21:29 ` kbuild test robot
2015-10-06 21:29 ` kbuild test robot [this message]
2015-10-06 21:30 ` Andrew
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=20151006212932.GA59274@xian \
--to=lkp@intel.com \
--cc=andrew@ncrmnt.org \
--cc=arve@android.com \
--cc=ccross@google.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=feng.tang@intel.com \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kbuild-all@01.org \
--cc=labbott@fedoraproject.org \
--cc=laura@labbott.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mitchelh@codeaurora.org \
--cc=riandrews@android.com \
--cc=robh+dt@kernel.org \
--cc=romlem@google.com \
--cc=sumit.semwal@linaro.org \
--cc=tom.gall@linaro.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;
as well as URLs for NNTP newsgroup(s).