From: kernel test robot <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: [email protected],
Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: [ammarfaizi2-block:testing/af/home 6/8] fs/btrfs/async-thread.c:411:41: error: 'struct btrfs_fs_info' has no member named 'hipri_workers'; did you mean 'fixup_workers'?
Date: Wed, 9 Aug 2023 00:19:29 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block testing/af/home
head: 8b2a24828c670d20cda3d69f5741e11e89f575f7
commit: 5f3624d1fef48864c37168c21cd1a1a1334649b8 [6/8] btrfs: Add wq_cpu_set=%s mount option
config: microblaze-randconfig-r034-20230808 (https://download.01.org/0day-ci/archive/20230809/[email protected]/config)
compiler: microblaze-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230809/[email protected]/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 <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
fs/btrfs/async-thread.c: In function 'btrfs_apply_workqueue_cpu_set':
>> fs/btrfs/async-thread.c:411:41: error: 'struct btrfs_fs_info' has no member named 'hipri_workers'; did you mean 'fixup_workers'?
411 | btrfs_apply_wq_cpu_set(fs_info, hipri_workers);
| ^~~~~~~~~~~~~
fs/btrfs/async-thread.c:402:47: note: in definition of macro 'btrfs_apply_wq_cpu_set'
402 | apply_wq_cpu_set_notice(INFO, (INFO)->WQ->normal_wq, # WQ)
| ^~
vim +411 fs/btrfs/async-thread.c
397
398 #define apply_wq_cpu_set(INFO, WQ) \
399 apply_wq_cpu_set_notice(INFO, (INFO)->WQ, # WQ)
400
401 #define btrfs_apply_wq_cpu_set(INFO, WQ) \
402 apply_wq_cpu_set_notice(INFO, (INFO)->WQ->normal_wq, # WQ)
403
404
405 void btrfs_apply_workqueue_cpu_set(struct btrfs_fs_info *fs_info)
406 {
407 if (!btrfs_test_opt(fs_info, WQ_CPU_SET))
408 return;
409
410 btrfs_apply_wq_cpu_set(fs_info, workers);
> 411 btrfs_apply_wq_cpu_set(fs_info, hipri_workers);
412 btrfs_apply_wq_cpu_set(fs_info, delalloc_workers);
413 btrfs_apply_wq_cpu_set(fs_info, flush_workers);
414 btrfs_apply_wq_cpu_set(fs_info, caching_workers);
415 btrfs_apply_wq_cpu_set(fs_info, fixup_workers);
416 apply_wq_cpu_set(fs_info, endio_workers);
417 apply_wq_cpu_set(fs_info, endio_meta_workers);
418 apply_wq_cpu_set(fs_info, rmw_workers);
419 btrfs_apply_wq_cpu_set(fs_info, endio_write_workers);
420 apply_wq_cpu_set(fs_info, compressed_write_workers);
421 btrfs_apply_wq_cpu_set(fs_info, endio_freespace_worker);
422 btrfs_apply_wq_cpu_set(fs_info, delayed_workers);
423 btrfs_apply_wq_cpu_set(fs_info, qgroup_rescan_workers);
424 apply_wq_cpu_set(fs_info, discard_ctl.discard_workers);
425 }
426
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-08 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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