All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arpitha Raghunandan <98.arpi@gmail.com>
To: Marco Elver <elver@google.com>, kernel test robot <lkp@intel.com>
Cc: Brendan Higgins <brendanhiggins@google.com>,
	skhan@linuxfoundation.org, Iurii Zaikin <yzaikin@google.com>,
	Theodore Ts'o <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	kbuild-all@lists.01.org,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	KUnit Development <kunit-dev@googlegroups.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] fs: ext4: Modify inode-test.c to use KUnit parameterized testing feature
Date: Wed, 28 Oct 2020 14:17:28 +0530	[thread overview]
Message-ID: <2721816d-53da-fa8a-d017-fe05bf6cb099@gmail.com> (raw)
In-Reply-To: <CANpmjNON4e6Gh7-NQw4CT4e--vOrH_rFyGi9U9TiUNS_zn+_vw@mail.gmail.com>

On 28/10/20 2:00 pm, Marco Elver wrote:
> On Wed, 28 Oct 2020 at 00:50, kernel test robot <lkp@intel.com> wrote:
>>
>> Hi Arpitha,
>>
>> Thank you for the patch! Perhaps something to improve:
>>
>> [auto build test WARNING on ext4/dev]
>> [also build test WARNING on linus/master v5.10-rc1 next-20201027]
>> [If your patch is applied to the wrong git tree, kindly drop us a note.
>> And when submitting patch, we suggest to use '--base' as documented in
>> https://git-scm.com/docs/git-format-patch]
>>
>> url:    https://github.com/0day-ci/linux/commits/Arpitha-Raghunandan/kunit-Support-for-Parameterized-Testing/20201028-015018
>> base:   https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
>> config: mips-randconfig-r016-20201027 (attached as .config)
>> compiler: mipsel-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://github.com/0day-ci/linux/commit/2de1e52708cd83d1dc4c718876683f6809045a98
>>         git remote add linux-review https://github.com/0day-ci/linux
>>         git fetch --no-tags linux-review Arpitha-Raghunandan/kunit-Support-for-Parameterized-Testing/20201028-015018
>>         git checkout 2de1e52708cd83d1dc4c718876683f6809045a98
>>         # save the attached .config to linux build tree
>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
>>
>> 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 >>):
>>
>>    In file included from fs/ext4/inode-test.c:7:
>>    fs/ext4/inode-test.c: In function 'ext4_inode_gen_params':
>>>> include/kunit/test.h:1735:58: warning: return discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
>>     1735 |   return __next - (array) < ARRAY_SIZE((array)) ? __next : NULL;   \
>>    fs/ext4/inode-test.c:214:1: note: in expansion of macro 'KUNIT_ARRAY_PARAM'
>>      214 | KUNIT_ARRAY_PARAM(ext4_inode, test_data);
>>          | ^~~~~~~~~~~~~~~~~
> 
> So this means we probably want to make the param_value, and the return
> and prev types of the generator "const void*".
> 
> Thanks,
> -- Marco
> 

Okay, I'll fix this.
Thanks!

  reply	other threads:[~2020-10-29  0:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 17:46 [PATCH v4 1/2] kunit: Support for Parameterized Testing Arpitha Raghunandan
2020-10-27 17:46 ` [Linux-kernel-mentees] " Arpitha Raghunandan
2020-10-27 17:47 ` [PATCH v4 2/2] fs: ext4: Modify inode-test.c to use KUnit parameterized testing feature Arpitha Raghunandan
2020-10-27 17:47   ` [Linux-kernel-mentees] " Arpitha Raghunandan
2020-10-27 23:49   ` kernel test robot
2020-10-27 23:49     ` kernel test robot
2020-10-28  8:30     ` Marco Elver
2020-10-28  8:30       ` Marco Elver
2020-10-28  8:47       ` Arpitha Raghunandan [this message]
2020-10-31 18:41   ` kernel test robot
2020-10-31 18:41     ` kernel test robot
2020-10-27 19:21 ` [PATCH v4 1/2] kunit: Support for Parameterized Testing Marco Elver
2020-10-27 19:21   ` [Linux-kernel-mentees] " Marco Elver via Linux-kernel-mentees
2020-10-28  8:45   ` Arpitha Raghunandan
2020-10-28  8:45     ` [Linux-kernel-mentees] " Arpitha Raghunandan
2020-11-05  7:31   ` Arpitha Raghunandan
2020-11-05  7:31     ` [Linux-kernel-mentees] " Arpitha Raghunandan
2020-11-05  8:30     ` Marco Elver
2020-11-05  8:30       ` [Linux-kernel-mentees] " Marco Elver via Linux-kernel-mentees
2020-11-05 14:30       ` Arpitha Raghunandan
2020-11-05 14:30         ` [Linux-kernel-mentees] " Arpitha Raghunandan
2020-11-05 15:02         ` Marco Elver
2020-11-05 15:02           ` [Linux-kernel-mentees] " Marco Elver via Linux-kernel-mentees
2020-11-05 19:55           ` Marco Elver
2020-11-05 19:55             ` [Linux-kernel-mentees] " Marco Elver via Linux-kernel-mentees
2020-11-06  5:54             ` Arpitha Raghunandan
2020-11-06  5:54               ` [Linux-kernel-mentees] " Arpitha Raghunandan
2020-11-06  8:11               ` Marco Elver
2020-11-06  8:11                 ` [Linux-kernel-mentees] " Marco Elver via Linux-kernel-mentees
2020-11-06 12:34                 ` Marco Elver
2020-11-06 12:34                   ` [Linux-kernel-mentees] " Marco Elver via Linux-kernel-mentees
2020-11-06 16:16                   ` Arpitha Raghunandan
2020-11-06 16:16                     ` [Linux-kernel-mentees] " Arpitha Raghunandan

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=2721816d-53da-fa8a-d017-fe05bf6cb099@gmail.com \
    --to=98.arpi@gmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=brendanhiggins@google.com \
    --cc=elver@google.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=skhan@linuxfoundation.org \
    --cc=tytso@mit.edu \
    --cc=yzaikin@google.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 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.