From: kernel test robot <lkp@intel.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
David Gow <davidgow@google.com>
Subject: lib/kunit/string-stream-test.c:73:9: sparse: sparse: incorrect type in initializer (different base types)
Date: Sat, 18 Nov 2023 19:23:17 +0800 [thread overview]
Message-ID: <202311181918.0mpCu2Xh-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 791c8ab095f71327899023223940dd52257a4173
commit: d1a0d699bfc00ae5b5e74bb640d791a93e825b68 kunit: string-stream: Add tests for freeing resource-managed string_stream
date: 9 weeks ago
config: x86_64-randconfig-x001-20230717 (https://download.01.org/0day-ci/archive/20231118/202311181918.0mpCu2Xh-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231118/202311181918.0mpCu2Xh-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202311181918.0mpCu2Xh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/kunit/string-stream-test.c:73:9: sparse: sparse: incorrect type in initializer (different base types) @@ expected long long left_value @@ got restricted gfp_t const __left @@
lib/kunit/string-stream-test.c:73:9: sparse: expected long long left_value
lib/kunit/string-stream-test.c:73:9: sparse: got restricted gfp_t const __left
>> lib/kunit/string-stream-test.c:73:9: sparse: sparse: incorrect type in initializer (different base types) @@ expected long long right_value @@ got restricted gfp_t const __right @@
lib/kunit/string-stream-test.c:73:9: sparse: expected long long right_value
lib/kunit/string-stream-test.c:73:9: sparse: got restricted gfp_t const __right
vim +73 lib/kunit/string-stream-test.c
61
62 /* Unmanaged string_stream object is initialized correctly. */
63 static void string_stream_unmanaged_init_test(struct kunit *test)
64 {
65 struct string_stream *stream;
66
67 stream = alloc_string_stream(GFP_KERNEL);
68 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, stream);
69 kunit_add_action(test, cleanup_raw_stream, stream);
70
71 KUNIT_EXPECT_EQ(test, stream->length, 0);
72 KUNIT_EXPECT_TRUE(test, list_empty(&stream->fragments));
> 73 KUNIT_EXPECT_EQ(test, stream->gfp, GFP_KERNEL);
74 KUNIT_EXPECT_FALSE(test, stream->append_newlines);
75
76 KUNIT_EXPECT_TRUE(test, string_stream_is_empty(stream));
77 }
78
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-18 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 11:23 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-18 0:52 lib/kunit/string-stream-test.c:73:9: sparse: sparse: incorrect type in initializer (different base types) kernel 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=202311181918.0mpCu2Xh-lkp@intel.com \
--to=lkp@intel.com \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rf@opensource.cirrus.com \
--cc=skhan@linuxfoundation.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