linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Gow <davidgow@google.com>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Brendan Higgins <brendanhiggins@google.com>,
	shuah@kernel.org
Cc: kbuild-all@lists.01.org, linux-kselftest@vger.kernel.org,
	kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org,
	David Gow <davidgow@google.com>
Subject: Re: [PATCH v3] fat: Add KUnit tests for checksums and timestamps
Date: Thu, 22 Oct 2020 14:28:01 +0800	[thread overview]
Message-ID: <202010221410.3YuswWrQ-lkp@intel.com> (raw)
In-Reply-To: <20201021061713.1545931-1-davidgow@google.com>

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

Hi David,

I love your patch! Yet something to improve:

[auto build test ERROR on c4d6fe7311762f2e03b3c27ad38df7c40c80cc93]

url:    https://github.com/0day-ci/linux/commits/David-Gow/fat-Add-KUnit-tests-for-checksums-and-timestamps/20201021-141819
base:    c4d6fe7311762f2e03b3c27ad38df7c40c80cc93
config: sparc64-randconfig-r034-20201022 (attached as .config)
compiler: sparc64-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/2395aa690e74265a3d09190ff5fc3628dcac9f09
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review David-Gow/fat-Add-KUnit-tests-for-checksums-and-timestamps/20201021-141819
        git checkout 2395aa690e74265a3d09190ff5fc3628dcac9f09
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sparc64 

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 >>):

>> fs/fat/inode.c:64:35: error: 'CONFIG_FAT_DEFAULT_CODEPAGE' undeclared here (not in a function); did you mean 'CONFIG_FAT_DEFAULT_IOCHARSET'?
      64 | static int fat_default_codepage = CONFIG_FAT_DEFAULT_CODEPAGE;
         |                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~
         |                                   CONFIG_FAT_DEFAULT_IOCHARSET

vim +64 fs/fat/inode.c

190a8843ded231 Conrad Meyer   2014-06-06  63  
^1da177e4c3f41 Linus Torvalds 2005-04-16 @64  static int fat_default_codepage = CONFIG_FAT_DEFAULT_CODEPAGE;
^1da177e4c3f41 Linus Torvalds 2005-04-16  65  static char fat_default_iocharset[] = CONFIG_FAT_DEFAULT_IOCHARSET;
^1da177e4c3f41 Linus Torvalds 2005-04-16  66  

---
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: 29678 bytes --]

      reply	other threads:[~2020-10-22  6:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21  6:17 [PATCH v3] fat: Add KUnit tests for checksums and timestamps David Gow
2020-10-22  6:28 ` 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=202010221410.3YuswWrQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brendanhiggins@google.com \
    --cc=davidgow@google.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=kbuild-all@lists.01.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@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).