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: [RFC PATCH kbuild] kbuild: kunit_stream_get_level() can be static
Date: Fri, 10 May 2019 15:32:07 +0800 [thread overview]
Message-ID: <20190510073207.GA2325@lkp-kbuild06> (raw)
In-Reply-To: <201905101508.nymn1QP2%lkp@intel.com>
Fixes: 7ab313d288d1 ("kbuild: enable building KUnit")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
kunit-stream.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kunit/kunit-stream.c b/kunit/kunit-stream.c
index 93c14ee..3d92646 100644
--- a/kunit/kunit-stream.c
+++ b/kunit/kunit-stream.c
@@ -11,7 +11,7 @@
#include <kunit/kunit-stream.h>
#include <kunit/string-stream.h>
-const char *kunit_stream_get_level(struct kunit_stream *this)
+static const char *kunit_stream_get_level(struct kunit_stream *this)
{
unsigned long flags;
const char *level;
prev parent 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:kunit 6/17] kunit/kunit-stream.c:14:12: sparse: sparse: symbol 'kunit_stream_get_level' was not declared. Should it be static? kbuild test robot
2019-05-10 7:32 ` kbuild test robot [this message]
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=20190510073207.GA2325@lkp-kbuild06 \
--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