From: kernel test robot <lkp@intel.com>
To: Baokun Li <libaokun1@huawei.com>, linux-ext4@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 1/4] ext4: unify the type of flexbg_size to unsigned int
Date: Mon, 23 Oct 2023 10:31:06 +0800 [thread overview]
Message-ID: <202310231017.HTcNT4ZK-lkp@intel.com> (raw)
In-Reply-To: <20231023013057.2117948-2-libaokun1@huawei.com>
Hi Baokun,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tytso-ext4/dev]
[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/Baokun-Li/ext4-unify-the-type-of-flexbg_size-to-unsigned-int/20231023-092711
base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
patch link: https://lore.kernel.org/r/20231023013057.2117948-2-libaokun1%40huawei.com
patch subject: [PATCH v2 1/4] ext4: unify the type of flexbg_size to unsigned int
reproduce: (https://download.01.org/0day-ci/archive/20231023/202310231017.HTcNT4ZK-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/202310231017.HTcNT4ZK-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:SPLIT_STRING: quoted string split across lines
#50: FILE: fs/ext4/resize.c:387:
printk(KERN_DEBUG "EXT4-fs: adding a flex group with "
+ "%u groups, flexbg size is %u:\n", flex_gd->count,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-23 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 1:30 [PATCH v2 0/4] ext4: fix WARN_ON in alloc_flex_gd() Baokun Li
2023-10-23 1:30 ` [PATCH v2 1/4] ext4: unify the type of flexbg_size to unsigned int Baokun Li
2023-10-23 2:31 ` kernel test robot [this message]
2023-10-23 1:30 ` [PATCH v2 2/4] ext4: remove unnecessary check from alloc_flex_gd() Baokun Li
2023-10-23 1:30 ` [PATCH v2 3/4] ext4: avoid online resizing failures due to oversized flex bg Baokun Li
2023-10-23 2:43 ` kernel test robot
2023-10-23 1:30 ` [PATCH v2 4/4] ext4: reduce unnecessary memory allocation in alloc_flex_gd() Baokun Li
2024-01-09 2:53 ` [PATCH v2 0/4] ext4: fix WARN_ON " Theodore Ts'o
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=202310231017.HTcNT4ZK-lkp@intel.com \
--to=lkp@intel.com \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--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 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.