From: kernel test robot <lkp@intel.com>
To: Yi Sun <yi.sun@unisoc.com>,
sunyibuaa@gmail.com, tj@kernel.org, jaegeuk@kernel.org,
chao@kernel.org
Cc: yunlongxing23@gmail.com, ebiggers@google.com,
kent.overstreet@linux.dev, jiangshanlai@gmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
oe-kbuild-all@lists.linux.dev, Hao_hao.Wang@unisoc.com
Subject: Re: [f2fs-dev] [PATCH 1/2] workqueue: add io priority to work_struct
Date: Wed, 26 Jun 2024 12:32:11 +0800 [thread overview]
Message-ID: <202406261201.0hc4qgvm-lkp@intel.com> (raw)
In-Reply-To: <20240621062617.595007-2-yi.sun@unisoc.com>
Hi Yi,
kernel test robot noticed the following build errors:
[auto build test ERROR on tj-wq/for-next]
[also build test ERROR on jaegeuk-f2fs/dev-test jaegeuk-f2fs/dev linus/master v6.10-rc5 next-20240625]
[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/Yi-Sun/workqueue-add-io-priority-to-work_struct/20240625-165935
base: https://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-next
patch link: https://lore.kernel.org/r/20240621062617.595007-2-yi.sun%40unisoc.com
patch subject: [PATCH 1/2] workqueue: add io priority to work_struct
config: arm-randconfig-003-20240626 (https://download.01.org/0day-ci/archive/20240626/202406261201.0hc4qgvm-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240626/202406261201.0hc4qgvm-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/202406261201.0hc4qgvm-lkp@intel.com/
All errors (new ones prefixed by >>):
arm-linux-gnueabi-ld: kernel/workqueue.o: in function `restore_work_task_ioprio':
>> workqueue.c:(.text+0xd2e): undefined reference to `set_task_ioprio'
arm-linux-gnueabi-ld: kernel/workqueue.o: in function `may_adjust_work_task_ioprio':
workqueue.c:(.text+0xd18): undefined reference to `set_task_ioprio'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-06-26 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 6:26 [f2fs-dev] [PATCH 0/2] add io priority feature to work and use it in f2fs fsverity work Yi Sun
2024-06-21 6:26 ` [f2fs-dev] [PATCH 1/2] workqueue: add io priority to work_struct Yi Sun
2024-06-21 8:00 ` Lai Jiangshan
2024-06-21 14:23 ` Kent Overstreet
2024-06-26 4:32 ` kernel test robot [this message]
2024-06-26 5:17 ` kernel test robot
2024-06-21 6:26 ` [f2fs-dev] [PATCH 2/2] f2fs: set f2fs verify work io priority Yi Sun
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=202406261201.0hc4qgvm-lkp@intel.com \
--to=lkp@intel.com \
--cc=Hao_hao.Wang@unisoc.com \
--cc=chao@kernel.org \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sunyibuaa@gmail.com \
--cc=tj@kernel.org \
--cc=yi.sun@unisoc.com \
--cc=yunlongxing23@gmail.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 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).