From: Ammar Faizi <[email protected]>
To: kernel test robot <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>
Subject: Re: [ammarfaizi2-block:testing/af/home] BUILD REGRESSION 8b2a24828c670d20cda3d69f5741e11e89f575f7
Date: Wed, 9 Aug 2023 13:00:23 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, Aug 09, 2023 at 11:00:15AM +0800, kernel test robot wrote:
> tree/branch: https://github.com/ammarfaizi2/linux-block testing/af/home
> branch HEAD: 8b2a24828c670d20cda3d69f5741e11e89f575f7 btrfs: Add `BTRFS_DEFAULT_MAX_THREAD_POOL_SIZE` macro
>
> Error/Warning reports:
>
> https://lore.kernel.org/oe-kbuild-all/[email protected]
> https://lore.kernel.org/oe-kbuild-all/[email protected]
>
> Error/Warning: (recently discovered and may have been fixed)
>
> fs/btrfs/async-thread.c:411:34: error: no member named 'hipri_workers' in 'struct btrfs_fs_info'; did you mean 'fixup_workers'?
> fs/btrfs/async-thread.c:411:41: error: 'struct btrfs_fs_info' has no member named 'hipri_workers'; did you mean 'fixup_workers'?
Ah yeah, since commit:
8bfec2e426e4 ("btrfs: remove hipri_workers workqueue")
the hipri_workers field no longer exists.
Thanks,
diff --git a/fs/btrfs/async-thread.c b/fs/btrfs/async-thread.c
index a8fb6a38f043d32d..eb54fe5c2acea7d7 100644
--- a/fs/btrfs/async-thread.c
+++ b/fs/btrfs/async-thread.c
@@ -408,7 +408,6 @@ void btrfs_apply_workqueue_cpu_set(struct btrfs_fs_info *fs_info)
return;
btrfs_apply_wq_cpu_set(fs_info, workers);
- btrfs_apply_wq_cpu_set(fs_info, hipri_workers);
btrfs_apply_wq_cpu_set(fs_info, delalloc_workers);
btrfs_apply_wq_cpu_set(fs_info, flush_workers);
btrfs_apply_wq_cpu_set(fs_info, caching_workers);
--
Ammar Faizi
prev parent reply other threads:[~2023-08-09 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 3:00 [ammarfaizi2-block:testing/af/home] BUILD REGRESSION 8b2a24828c670d20cda3d69f5741e11e89f575f7 kernel test robot
2023-08-09 6:00 ` Ammar Faizi [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 \
[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