From: kernel test robot <lkp@intel.com>
To: Max Kellermann <max.kellermann@ionos.com>,
jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, amir73il@gmail.com,
max.kellermann@ionos.com
Subject: Re: [PATCH 4/4] arch: register inotify_add_watch_at
Date: Tue, 19 Sep 2023 04:24:01 +0800 [thread overview]
Message-ID: <202309190447.Md4xeYhu-lkp@intel.com> (raw)
In-Reply-To: <20230918123217.932179-4-max.kellermann@ionos.com>
Hi Max,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/x86/asm]
[also build test ERROR on linus/master v6.6-rc2]
[cannot apply to jack-fs/fsnotify arm64/for-next/core next-20230918]
[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/Max-Kellermann/inotify_user-move-code-to-do_inotify_add_watch/20230918-203410
base: tip/x86/asm
patch link: https://lore.kernel.org/r/20230918123217.932179-4-max.kellermann%40ionos.com
patch subject: [PATCH 4/4] arch: register inotify_add_watch_at
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20230919/202309190447.Md4xeYhu-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230919/202309190447.Md4xeYhu-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309190447.Md4xeYhu-lkp@intel.com/
All errors (new ones prefixed by >>):
>> or1k-linux-ld: arch/openrisc/kernel/sys_call_table.o:(.data+0x718): undefined reference to `sys_inotify_add_watch_at'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-09-18 20:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 12:32 [PATCH 1/4] inotify_user: pass directory fd to inotify_find_inode() Max Kellermann
2023-09-18 12:32 ` [PATCH 2/4] inotify_user: move code to do_inotify_add_watch() Max Kellermann
2023-09-18 12:32 ` [PATCH 3/4] inotify_user: add system call inotify_add_watch_at() Max Kellermann
2023-09-18 12:40 ` Jan Kara
2023-09-18 13:57 ` Max Kellermann
2023-09-18 14:23 ` Jan Kara
2023-09-18 15:28 ` Amir Goldstein
2023-09-18 18:05 ` inotify maintenance status Amir Goldstein
2023-09-19 7:16 ` Amir Goldstein
2023-09-19 9:08 ` Max Kellermann
2023-09-19 10:01 ` Jan Kara
2023-09-19 10:42 ` Amir Goldstein
2023-09-19 10:48 ` Max Kellermann
2023-09-19 10:42 ` Max Kellermann
2023-09-19 10:58 ` Amir Goldstein
2023-09-19 11:21 ` Max Kellermann
2023-09-19 12:21 ` Amir Goldstein
2023-09-19 12:51 ` Max Kellermann
2023-09-19 13:01 ` Amir Goldstein
2023-09-19 13:11 ` Max Kellermann
2023-09-19 13:22 ` Amir Goldstein
2023-09-19 13:41 ` Max Kellermann
2023-09-19 13:56 ` Amir Goldstein
2023-09-19 13:28 ` Jan Kara
2023-09-19 13:48 ` Max Kellermann
2023-09-19 9:26 ` Christian Brauner
2023-09-19 9:48 ` Jan Kara
2023-09-19 14:55 ` Amir Goldstein
2023-09-18 19:45 ` [PATCH 3/4] inotify_user: add system call inotify_add_watch_at() Max Kellermann
2023-09-18 12:32 ` [PATCH 4/4] arch: register inotify_add_watch_at Max Kellermann
2023-09-18 20:24 ` kernel test robot
2023-09-18 20:24 ` 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=202309190447.Md4xeYhu-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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).