From: kbuild test robot <lkp@intel.com>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: kbuild-all@01.org, linux-kbuild@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: [kbuild:kunit 6/17] kunit/kunit-stream.c:14:12: sparse: sparse: symbol 'kunit_stream_get_level' was not declared. Should it be static?
Date: Fri, 10 May 2019 15:32:05 +0800 [thread overview]
Message-ID: <201905101508.nymn1QP2%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kunit
head: c505c0b2e6237c729634327c178f5b0094f1c958
commit: 7ab313d288d1c686ae39c7052f6ed6426ed38b54 [6/17] kbuild: enable building KUnit
reproduce:
# apt-get install sparse
git checkout 7ab313d288d1c686ae39c7052f6ed6426ed38b54
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> kunit/kunit-stream.c:14:12: sparse: sparse: symbol 'kunit_stream_get_level' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-05-10 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 7:32 kbuild test robot [this message]
2019-05-10 7:32 ` [RFC PATCH kbuild] kbuild: kunit_stream_get_level() can be static kbuild test robot
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=201905101508.nymn1QP2%lkp@intel.com \
--to=lkp@intel.com \
--cc=brendanhiggins@google.com \
--cc=kbuild-all@01.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=yamada.masahiro@socionext.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