All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sheng Yong <shengyong@oppo.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] f2fs: expand f2fs_compr_option to allow ioctl setting compression level
Date: Fri, 31 Mar 2023 06:26:40 +0800	[thread overview]
Message-ID: <202303310601.ffuatWCu-lkp@intel.com> (raw)
In-Reply-To: <20230330153719.3085164-1-shengyong@oppo.com>

Hi Sheng,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on jaegeuk-f2fs/dev-test]
[also build test ERROR on jaegeuk-f2fs/dev next-20230330]
[cannot apply to linus/master v6.3-rc4]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Sheng-Yong/f2fs-expand-f2fs_compr_option-to-allow-ioctl-setting-compression-level/20230330-233928
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
patch link:    https://lore.kernel.org/r/20230330153719.3085164-1-shengyong%40oppo.com
patch subject: [RFC PATCH] f2fs: expand f2fs_compr_option to allow ioctl setting compression level
config: x86_64-randconfig-a015 (https://download.01.org/0day-ci/archive/20230331/202303310601.ffuatWCu-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
        # https://github.com/intel-lab-lkp/linux/commit/d454d77b29654af47145c3ff3b9a59714f84ca6a
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Sheng-Yong/f2fs-expand-f2fs_compr_option-to-allow-ioctl-setting-compression-level/20230330-233928
        git checkout d454d77b29654af47145c3ff3b9a59714f84ca6a
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 olddefconfig
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303310601.ffuatWCu-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from <command-line>:
>> ./usr/include/linux/f2fs.h:109:37: error: C++ style comments are not allowed in ISO C90
     109 |                         __u8 value; // MSB 4 bit is version, LSB 4 bit is algorithm
         |                                     ^
   ./usr/include/linux/f2fs.h:109:37: note: (this will be reported only once per input file)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests

      parent reply	other threads:[~2023-03-30 22:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 15:37 [f2fs-dev] [RFC PATCH] f2fs: expand f2fs_compr_option to allow ioctl setting compression level Sheng Yong via Linux-f2fs-devel
2023-03-30 15:37 ` Sheng Yong
2023-03-30 16:15 ` [f2fs-dev] " Yangtao Li via Linux-f2fs-devel
2023-03-30 16:15   ` Yangtao Li
2023-03-31  1:30   ` [f2fs-dev] " Sheng Yong via Linux-f2fs-devel
2023-03-31  1:30     ` Sheng Yong
2023-03-30 21:25 ` kernel test robot
2023-03-30 22:26 ` kernel 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=202303310601.ffuatWCu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shengyong@oppo.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.