From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: Re: [PATCH 1/7] btrfs: Use percpu refcounting for block groups
Date: Tue, 13 Jan 2026 11:32:49 +0100 [thread overview]
Message-ID: <202601131155.ulOGAl1n-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "high confidence checkpatch report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <0102019bb2ff56b7-9302e783-c17d-452d-b6a7-11f773776ae7-000000@eu-west-1.amazonses.com>
References: <0102019bb2ff56b7-9302e783-c17d-452d-b6a7-11f773776ae7-000000@eu-west-1.amazonses.com>
TO: Martin Raiber <martin@urbackup.org>
TO: linux-btrfs@vger.kernel.org
Hi Martin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on kdave/for-next]
[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/Martin-Raiber/btrfs-Use-percpu-semaphore-for-space-info-groups_sem/20260113-070107
base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link: https://lore.kernel.org/r/0102019bb2ff56b7-9302e783-c17d-452d-b6a7-11f773776ae7-000000%40eu-west-1.amazonses.com
patch subject: [PATCH 1/7] btrfs: Use percpu refcounting for block groups
:::::: branch date: 12 hours ago
:::::: commit date: 12 hours ago
reproduce: (https://download.01.org/0day-ci/archive/20260113/202601131155.ulOGAl1n-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#57: FILE: fs/btrfs/block-group.c:166:
+ /*
+ * If there was a failure to cleanup a log tree, very likely due
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#72: FILE: fs/btrfs/block-group.c:177:
+ /*
+ * A block_group shouldn't be on the discard_list anymore.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-13 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 10:32 kernel test robot [this message]
[not found] <20260112161549.2786827-1-martin@urbackup.org>
2026-01-12 16:17 ` [PATCH 1/7] btrfs: Use percpu refcounting for block groups Martin Raiber
2026-01-12 22:32 ` Boris Burkov
2026-01-14 6:06 ` kernel test robot
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=202601131155.ulOGAl1n-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 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.