From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [iio:testing 19/19] drivers/iio/test/iio-test-format.c:98:1: warning: the frame size of 2336 bytes is larger than 2048 bytes
Date: Mon, 15 Feb 2021 22:55:25 +0800 [thread overview]
Message-ID: <202102152219.ngAFGYOx-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3926 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git testing
head: 3347b9d6388587963d199b107278f89f05277a1b
commit: 3347b9d6388587963d199b107278f89f05277a1b [19/19] iio: Add basic unit test for iio_format_value()
config: powerpc-allyesconfig (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?id=3347b9d6388587963d199b107278f89f05277a1b
git remote add iio https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
git fetch --no-tags iio testing
git checkout 3347b9d6388587963d199b107278f89f05277a1b
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/iio/test/iio-test-format.c: In function 'iio_test_iio_format_value_fixedpoint':
>> drivers/iio/test/iio-test-format.c:98:1: warning: the frame size of 2336 bytes is larger than 2048 bytes [-Wframe-larger-than=]
98 | }
| ^
vim +98 drivers/iio/test/iio-test-format.c
41
42 static void iio_test_iio_format_value_fixedpoint(struct kunit *test)
43 {
44 char *buf = kunit_kmalloc(test, PAGE_SIZE, GFP_KERNEL);
45 int values[2];
46 int ret;
47
48 /* positive >= 1 */
49 values[0] = 1;
50 values[1] = 10;
51
52 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_MICRO, 2, values);
53 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "1.000010\n");
54
55 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_MICRO_DB, 2, values);
56 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "1.000010 dB\n");
57
58 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_NANO, 2, values);
59 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "1.000000010\n");
60
61 /* positive < 1 */
62 values[0] = 0;
63 values[1] = 12;
64
65 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_MICRO, 2, values);
66 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "0.000012\n");
67
68 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_MICRO_DB, 2, values);
69 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "0.000012 dB\n");
70
71 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_NANO, 2, values);
72 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "0.000000012\n");
73
74 /* negative <= -1 */
75 values[0] = -1;
76 values[1] = 10;
77
78 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_MICRO, 2, values);
79 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-1.000010\n");
80
81 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_MICRO_DB, 2, values);
82 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-1.000010 dB\n");
83
84 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_NANO, 2, values);
85 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-1.000000010\n");
86
87 /* negative > -1 */
88 values[0] = 0;
89 values[1] = -123;
90 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_MICRO, 2, values);
91 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-0.000123\n");
92
93 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_MICRO_DB, 2, values);
94 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-0.000123 dB\n");
95
96 ret = iio_format_value(buf, IIO_VAL_INT_PLUS_NANO, 2, values);
97 IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-0.000000123\n");
> 98 }
99
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 72550 bytes --]
reply other threads:[~2021-02-15 14:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202102152219.ngAFGYOx-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.