linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andriy Tryshnivskyy <andriy.tryshnivskyy@opensynergy.com>,
	jbhayana@google.com, jic23@kernel.org
Cc: kbuild-all@lists.01.org, lars@metafoo.de,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vasyl.Vavrychuk@opensynergy.com, andy.shevchenko@gmail.com,
	andriy.tryshnivskyy@opensynergy.com
Subject: Re: [PATCH v1 2/2] iio: test: Add test for IIO_VAL_INT_64.
Date: Sat, 6 Nov 2021 04:20:39 +0800	[thread overview]
Message-ID: <202111060417.ft7v5mHH-lkp@intel.com> (raw)
In-Reply-To: <20211105100501.1904-3-andriy.tryshnivskyy@opensynergy.com>

[-- Attachment #1: Type: text/plain, Size: 4164 bytes --]

Hi Andriy,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on 7d2a07b769330c34b4deabeed939325c77a7ec2f]

url:    https://github.com/0day-ci/linux/commits/Andriy-Tryshnivskyy/iio-test-Add-test-for-IIO_VAL_INT_64/20211105-180624
base:   7d2a07b769330c34b4deabeed939325c77a7ec2f
config: arc-buildonly-randconfig-r002-20211105 (attached as .config)
compiler: arc-elf-gcc (GCC) 11.2.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://github.com/0day-ci/linux/commit/679e11158271ed8c6219060b06dca25dce946859
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Andriy-Tryshnivskyy/iio-test-Add-test-for-IIO_VAL_INT_64/20211105-180624
        git checkout 679e11158271ed8c6219060b06dca25dce946859
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash drivers/iio/test/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/iio/test/iio-test-format.c: In function 'iio_test_iio_format_value_integer_64':
>> drivers/iio/test/iio-test-format.c:213:37: error: 'IIO_VAL_INT_64' undeclared (first use in this function); did you mean 'IIO_VAL_INT'?
     213 |         ret = iio_format_value(buf, IIO_VAL_INT_64, ARRAY_SIZE(values), values);
         |                                     ^~~~~~~~~~~~~~
         |                                     IIO_VAL_INT
   drivers/iio/test/iio-test-format.c:213:37: note: each undeclared identifier is reported only once for each function it appears in


vim +213 drivers/iio/test/iio-test-format.c

   199	
   200	static void iio_test_iio_format_value_integer_64(struct kunit *test)
   201	{
   202		int values[2];
   203		s64 value;
   204		char *buf;
   205		int ret;
   206	
   207		buf = kunit_kmalloc(test, PAGE_SIZE, GFP_KERNEL);
   208		KUNIT_ASSERT_NOT_ERR_OR_NULL(test, buf);
   209	
   210		value = 24;
   211		values[0] = lower_32_bits(value);
   212		values[1] = upper_32_bits(value);
 > 213		ret = iio_format_value(buf, IIO_VAL_INT_64, ARRAY_SIZE(values), values);
   214		IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "24\n");
   215	
   216		value = -24;
   217		values[0] = lower_32_bits(value);
   218		values[1] = upper_32_bits(value);
   219		ret = iio_format_value(buf, IIO_VAL_INT_64, ARRAY_SIZE(values), values);
   220		IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-24\n");
   221	
   222		value = 0;
   223		values[0] = lower_32_bits(value);
   224		values[1] = upper_32_bits(value);
   225		ret = iio_format_value(buf, IIO_VAL_INT_64, ARRAY_SIZE(values), values);
   226		IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "0\n");
   227	
   228		value = UINT_MAX;
   229		values[0] = lower_32_bits(value);
   230		values[1] = upper_32_bits(value);
   231		ret = iio_format_value(buf, IIO_VAL_INT_64, ARRAY_SIZE(values), values);
   232		IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "4294967295\n");
   233	
   234		value = -((s64)UINT_MAX);
   235		values[0] = lower_32_bits(value);
   236		values[1] = upper_32_bits(value);
   237		ret = iio_format_value(buf, IIO_VAL_INT_64, ARRAY_SIZE(values), values);
   238		IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-4294967295\n");
   239	
   240		value = LLONG_MAX;
   241		values[0] = lower_32_bits(value);
   242		values[1] = upper_32_bits(value);
   243		ret = iio_format_value(buf, IIO_VAL_INT_64, ARRAY_SIZE(values), values);
   244		IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "9223372036854775807\n");
   245	
   246		value = LLONG_MIN;
   247		values[0] = lower_32_bits(value);
   248		values[1] = upper_32_bits(value);
   249		ret = iio_format_value(buf, IIO_VAL_INT_64, ARRAY_SIZE(values), values);
   250		IIO_TEST_FORMAT_EXPECT_EQ(test, buf, ret, "-9223372036854775808\n");
   251	}
   252	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26599 bytes --]

  reply	other threads:[~2021-11-05 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 10:04 [PATCH v1 0/2] iio: test: Add test for IIO_VAL_INT_64 Andriy Tryshnivskyy
2021-11-05 10:05 ` [PATCH v1 1/2] iio: test: Add check against NULL for buffer in tests Andriy Tryshnivskyy
2021-11-05 10:16   ` Andy Shevchenko
2021-11-13 16:52     ` Jonathan Cameron
2021-11-27 18:53       ` Jonathan Cameron
2021-11-28 18:23         ` Andriy Tryshnivskyy
2021-11-05 10:05 ` [PATCH v1 2/2] iio: test: Add test for IIO_VAL_INT_64 Andriy Tryshnivskyy
2021-11-05 20:20   ` kernel test robot [this message]
2021-11-05 10:17 ` [PATCH v1 0/2] " Andy Shevchenko
2021-11-05 10:26   ` Andriy Tryshnivskyy

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=202111060417.ft7v5mHH-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Vasyl.Vavrychuk@opensynergy.com \
    --cc=andriy.tryshnivskyy@opensynergy.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=jbhayana@google.com \
    --cc=jic23@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).