From: Joseph Wright <rjosephwright@gmail.com>
To: gregkh@linuxfoundation.org, arve@android.com, riandrews@android.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Joseph Wright <rjosephwright@gmail.com>
Subject: [PATCH v2 1/2] Staging: android/ion: fix sparse warnings
Date: Wed, 12 Jul 2017 04:51:13 +0000 [thread overview]
Message-ID: <20170712045114.21508-2-rjosephwright@gmail.com> (raw)
In-Reply-To: <20170712045114.21508-1-rjosephwright@gmail.com>
Declare functions to fix sparse warnings:
ion_carveout_heap.c:115:17: warning: symbol 'ion_carveout_heap_create' \
was not declared. Should it be static?
ion_chunk_heap.c:120:17: warning: symbol 'ion_chunk_heap_create' \
was not declared. Should it be static?
Signed-off-by: Joseph Wright <rjosephwright@gmail.com>
---
Changes in v2:
- Split into multiple patches
drivers/staging/android/ion/ion.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/staging/android/ion/ion.h b/drivers/staging/android/ion/ion.h
index fa9ed81..fda1e91 100644
--- a/drivers/staging/android/ion/ion.h
+++ b/drivers/staging/android/ion/ion.h
@@ -358,4 +358,8 @@ long ion_ioctl(struct file *filp, unsigned int cmd, unsigned long arg);
int ion_query_heaps(struct ion_heap_query *query);
+struct ion_heap *ion_chunk_heap_create(struct ion_platform_heap *heap_data);
+
+struct ion_heap *ion_carveout_heap_create(struct ion_platform_heap *heap_data);
+
#endif /* _ION_H */
--
2.9.3
next prev parent reply other threads:[~2017-07-12 4:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 4:51 [PATCH v2 0/2] " Joseph Wright
2017-07-12 4:51 ` Joseph Wright [this message]
2017-07-12 5:22 ` [PATCH v2 1/2] " Frans Klaver
2017-07-12 4:51 ` [PATCH v2 2/2] Staging: android/ion: fix sparse warning Joseph Wright
2017-07-12 5:23 ` Frans Klaver
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=20170712045114.21508-2-rjosephwright@gmail.com \
--to=rjosephwright@gmail.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.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
all inboxes | Powered by JetHome®