From: kernel test robot <lkp@intel.com>
To: guanjing <guanjing@cmss.chinamobile.com>,
krisman@kernel.org, hughd@google.com, akpm@linux-foundation.org,
andrealmeid@igalia.com, brauner@kernel.org, tytso@mit.edu
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
guanjing <guanjing@cmss.chinamobile.com>
Subject: Re: [PATCH v1] tmpfs: Unsigned expression compared with zero
Date: Fri, 22 Nov 2024 11:31:16 +0800 [thread overview]
Message-ID: <202411221128.qSNFAkty-lkp@intel.com> (raw)
In-Reply-To: <20241120105150.24008-1-guanjing@cmss.chinamobile.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 2408 bytes --]
Hi guanjing,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on linus/master next-20241121]
[cannot apply to v6.12]
[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/guanjing/tmpfs-Unsigned-expression-compared-with-zero/20241121-152806
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20241120105150.24008-1-guanjing%40cmss.chinamobile.com
patch subject: [PATCH v1] tmpfs: Unsigned expression compared with zero
config: arc-randconfig-001-20241122 (https://download.01.org/0day-ci/archive/20241122/202411221128.qSNFAkty-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241122/202411221128.qSNFAkty-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/202411221128.qSNFAkty-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/unicode/utf8-core.c:225: warning: Function parameter or struct member 'version_str' not described in 'utf8_parse_version'
vim +225 fs/unicode/utf8-core.c
9d53690f0d4e56 Gabriel Krisman Bertazi 2019-04-25 216
142fa60f61f938 André Almeida 2024-10-21 217 /**
142fa60f61f938 André Almeida 2024-10-21 218 * utf8_parse_version - Parse a UTF-8 version number from a string
142fa60f61f938 André Almeida 2024-10-21 219 *
142fa60f61f938 André Almeida 2024-10-21 220 * @version: input string
142fa60f61f938 André Almeida 2024-10-21 221 *
fd9b2236cc1a2d guanjing 2024-11-20 222 * Returns 0 on success, negative code on error
142fa60f61f938 André Almeida 2024-10-21 223 */
fd9b2236cc1a2d guanjing 2024-11-20 224 int utf8_parse_version(char *version_str, unsigned int *version)
142fa60f61f938 André Almeida 2024-10-21 @225 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-11-22 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 10:51 [PATCH v1] tmpfs: Unsigned expression compared with zero guanjing
2024-11-20 11:10 ` André Almeida
2024-11-22 3:31 ` kernel test robot [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 \
--in-reply-to=202411221128.qSNFAkty-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=brauner@kernel.org \
--cc=guanjing@cmss.chinamobile.com \
--cc=hughd@google.com \
--cc=krisman@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tytso@mit.edu \
/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