From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: kernel test robot <lkp@intel.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca, jaegeuk@kernel.org,
kbuild-all@lists.01.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, ebiggers@kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v2 7/7] f2fs: Reuse generic_ci_match for ci comparisons
Date: Fri, 29 Apr 2022 13:36:04 -0400 [thread overview]
Message-ID: <87ee1fx057.fsf@collabora.com> (raw)
In-Reply-To: <202204291733.QRyzoWB6-lkp@intel.com> (kernel test robot's message of "Fri, 29 Apr 2022 17:12:49 +0800")
kernel test robot <lkp@intel.com> writes:
> Hi Gabriel,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on tytso-ext4/dev]
> [also build test ERROR on jaegeuk-f2fs/dev-test linus/master v5.18-rc4 next-20220428]
> [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/intel-lab-lkp/linux/commits/Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220429-061233
> base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
> config: microblaze-buildonly-randconfig-r004-20220428 (https://download.01.org/0day-ci/archive/20220429/202204291733.QRyzoWB6-lkp@intel.com/config)
> compiler: microblaze-linux-gcc (GCC) 11.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/intel-lab-lkp/linux/commit/8955999168ad8e2d440ec534ebe26830da9bc6f6
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220429-061233
> git checkout 8955999168ad8e2d440ec534ebe26830da9bc6f6
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=microblaze SHELL=/bin/bash
>
> 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 >>, old ones prefixed by <<):
>
>>> ERROR: modpost: "generic_ci_match" [fs/f2fs/f2fs.ko] undefined!
> ERROR: modpost: "generic_ci_match" [fs/ext4/ext4.ko] undefined!
Missing an EXPORT_SYMBOL, I guess. sorry for the noise. will fix and
resend.
--
Gabriel Krisman Bertazi
WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: kernel test robot <lkp@intel.com>
Cc: kernel@collabora.com, tytso@mit.edu,
linux-f2fs-devel@lists.sourceforge.net, ebiggers@kernel.org,
adilger.kernel@dilger.ca, jaegeuk@kernel.org,
kbuild-all@lists.01.org, linux-ext4@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2 7/7] f2fs: Reuse generic_ci_match for ci comparisons
Date: Fri, 29 Apr 2022 13:36:04 -0400 [thread overview]
Message-ID: <87ee1fx057.fsf@collabora.com> (raw)
In-Reply-To: <202204291733.QRyzoWB6-lkp@intel.com> (kernel test robot's message of "Fri, 29 Apr 2022 17:12:49 +0800")
kernel test robot <lkp@intel.com> writes:
> Hi Gabriel,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on tytso-ext4/dev]
> [also build test ERROR on jaegeuk-f2fs/dev-test linus/master v5.18-rc4 next-20220428]
> [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/intel-lab-lkp/linux/commits/Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220429-061233
> base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
> config: microblaze-buildonly-randconfig-r004-20220428 (https://download.01.org/0day-ci/archive/20220429/202204291733.QRyzoWB6-lkp@intel.com/config)
> compiler: microblaze-linux-gcc (GCC) 11.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/intel-lab-lkp/linux/commit/8955999168ad8e2d440ec534ebe26830da9bc6f6
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220429-061233
> git checkout 8955999168ad8e2d440ec534ebe26830da9bc6f6
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=microblaze SHELL=/bin/bash
>
> 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 >>, old ones prefixed by <<):
>
>>> ERROR: modpost: "generic_ci_match" [fs/f2fs/f2fs.ko] undefined!
> ERROR: modpost: "generic_ci_match" [fs/ext4/ext4.ko] undefined!
Missing an EXPORT_SYMBOL, I guess. sorry for the noise. will fix and
resend.
--
Gabriel Krisman Bertazi
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 7/7] f2fs: Reuse generic_ci_match for ci comparisons
Date: Fri, 29 Apr 2022 13:36:04 -0400 [thread overview]
Message-ID: <87ee1fx057.fsf@collabora.com> (raw)
In-Reply-To: <202204291733.QRyzoWB6-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2065 bytes --]
kernel test robot <lkp@intel.com> writes:
> Hi Gabriel,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on tytso-ext4/dev]
> [also build test ERROR on jaegeuk-f2fs/dev-test linus/master v5.18-rc4 next-20220428]
> [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/intel-lab-lkp/linux/commits/Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220429-061233
> base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
> config: microblaze-buildonly-randconfig-r004-20220428 (https://download.01.org/0day-ci/archive/20220429/202204291733.QRyzoWB6-lkp(a)intel.com/config)
> compiler: microblaze-linux-gcc (GCC) 11.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/intel-lab-lkp/linux/commit/8955999168ad8e2d440ec534ebe26830da9bc6f6
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220429-061233
> git checkout 8955999168ad8e2d440ec534ebe26830da9bc6f6
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=microblaze SHELL=/bin/bash
>
> 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 >>, old ones prefixed by <<):
>
>>> ERROR: modpost: "generic_ci_match" [fs/f2fs/f2fs.ko] undefined!
> ERROR: modpost: "generic_ci_match" [fs/ext4/ext4.ko] undefined!
Missing an EXPORT_SYMBOL, I guess. sorry for the noise. will fix and
resend.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2022-04-29 17:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 22:10 [PATCH v2 0/7] Clean up the case-insenstive lookup path Gabriel Krisman Bertazi
2022-04-28 22:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-04-28 22:10 ` [PATCH v2 1/7] ext4: Match the f2fs ci_compare implementation Gabriel Krisman Bertazi
2022-04-28 22:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-04-28 22:10 ` [PATCH v2 2/7] ext4: Simplify the handling of cached insensitive names Gabriel Krisman Bertazi
2022-04-28 22:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-04-28 22:10 ` [PATCH v2 3/7] ext4: Implement ci comparison using unicode_name Gabriel Krisman Bertazi
2022-04-28 22:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-04-28 22:10 ` [PATCH v2 4/7] ext4: Simplify hash check on ext4_match Gabriel Krisman Bertazi
2022-04-28 22:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-04-28 22:10 ` [PATCH v2 5/7] ext4: Log error when lookup of encoded dentry fails Gabriel Krisman Bertazi
2022-04-28 22:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-04-28 22:10 ` [PATCH v2 6/7] ext4: Move ext4_match_ci into libfs Gabriel Krisman Bertazi
2022-04-28 22:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-04-29 5:39 ` kernel test robot
2022-04-29 5:39 ` [f2fs-dev] " kernel test robot
2022-04-28 22:10 ` [PATCH v2 7/7] f2fs: Reuse generic_ci_match for ci comparisons Gabriel Krisman Bertazi
2022-04-28 22:10 ` [f2fs-dev] " Gabriel Krisman Bertazi
2022-04-29 9:12 ` kernel test robot
2022-04-29 9:12 ` [f2fs-dev] " kernel test robot
2022-04-29 17:36 ` Gabriel Krisman Bertazi [this message]
2022-04-29 17:36 ` Gabriel Krisman Bertazi
2022-04-29 17:36 ` [f2fs-dev] " Gabriel Krisman Bertazi
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=87ee1fx057.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=adilger.kernel@dilger.ca \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kernel@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=lkp@intel.com \
--cc=tytso@mit.edu \
/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.