From: Shuah Khan <shuah@kernel.org>
To: Li Zhijian <lizhijian@cn.fujitsu.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Pintu Agarwal <pintu.ping@gmail.com>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 2/3] selftests/android: initialize heap_type to avoid compiling warning
Date: Tue, 10 Jul 2018 08:50:36 -0600 [thread overview]
Message-ID: <1f24bf06-88cb-8d09-febf-02ff55ec263a@kernel.org> (raw)
In-Reply-To: <1530503634-32241-3-git-send-email-lizhijian@cn.fujitsu.com>
Hi Li Zhijian,
On 07/01/2018 09:53 PM, Li Zhijian wrote:
> root@vm-lkp-nex04-8G-7 ~/linux-v4.18-rc2/tools/testing/selftests/android# make
> make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
> make[1]: Entering directory '/root/linux-v4.18-rc2/tools/testing/selftests/android/ion'
> gcc -I. -I../../../../../drivers/staging/android/uapi/ -I../../../../../usr/include/ -Wall -O2 -g ionapp_export.c ipcsocket.c ionutils.c -o ionapp_export
> ionapp_export.c: In function 'main':
> ionapp_export.c:91:2: warning: 'heap_type' may be used uninitialized in
> this function [-Wmaybe-uninitialized]
> printf("heap_type: %ld, heap_size: %ld\n", heap_type, heap_size);
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> CC: Shuah Khan <shuah@kernel.org>
> CC: Pintu Agarwal <pintu.ping@gmail.com>
> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> ---
> tools/testing/selftests/android/ion/ionapp_export.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/tools/testing/selftests/android/ion/ionapp_export.c b/tools/testing/selftests/android/ion/ionapp_export.c
> index a944e72..e3435c2 100644
> --- a/tools/testing/selftests/android/ion/ionapp_export.c
> +++ b/tools/testing/selftests/android/ion/ionapp_export.c
> @@ -49,6 +49,7 @@ int main(int argc, char *argv[])
> return -1;
> }
>
> + heap_type = -1UL;
Initialize it to one of the valid types. ION_HEAP_TYPE_SYSTEM
is one choice.
> heap_size = 0;
> flags = 0;
>
> @@ -82,6 +83,12 @@ int main(int argc, char *argv[])
> }
> }
>
> + if (heap_type == -1UL) {
> + printf("heap_type is invalid\n");
> + print_usage(argc, argv);
> + exit(1);
> + }
This check isn't necessary. The test requires two arguments,
-i <heap id> and -s <size in bytes> and won't run without either
one of them. heap_type is going to be ION_HEAP_TYPE_SYSTEM or
ION_HEAP_TYPE_SYSTEM_CONTIG at this point.
Interesting. Looks like this test doesn't cover all ion_heap_types.
thanks,
-- Shuah
next prev parent reply other threads:[~2018-07-10 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 3:53 [PATCH 0/3] fix selftests compiling errors and warnings Li Zhijian
2018-07-02 3:53 ` [PATCH 1/3] selftests/android: fix compiling error Li Zhijian
2018-07-02 3:53 ` [PATCH 2/3] selftests/android: initialize heap_type to avoid compiling warning Li Zhijian
2018-07-02 3:53 ` [PATCH 3/3] selftests/gpio: unset OUTPUT for build tools/gpio Li Zhijian
2018-07-10 14:50 ` Shuah Khan [this message]
2018-07-10 17:16 ` [PATCH 2/3] selftests/android: initialize heap_type to avoid compiling warning Pintu Kumar
2018-07-10 8:38 ` [PATCH 0/3] fix selftests compiling errors and warnings Li Zhijian
2018-07-10 14:08 ` Shuah Khan
2018-07-11 1:37 ` Li Zhijian
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=1f24bf06-88cb-8d09-febf-02ff55ec263a@kernel.org \
--to=shuah@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizhijian@cn.fujitsu.com \
--cc=pintu.ping@gmail.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®