From: kernel test robot <lkp@intel.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 17/30] lib/string.c: strsep_no_empty()
Date: Wed, 31 Aug 2022 14:41:09 +0800 [thread overview]
Message-ID: <202208311418.jkohaAzL-lkp@intel.com> (raw)
In-Reply-To: <20220830214919.53220-18-surenb@google.com>
Hi Suren,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[also build test WARNING on v6.0-rc3]
[cannot apply to vbabka-slab/for-next tip/sched/core xen-tip/linux-next next-20220830]
[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/Suren-Baghdasaryan/Code-tagging-framework-and-applications/20220831-055155
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git dcf8e5633e2e69ad60b730ab5905608b756a032f
config: hexagon-randconfig-r045-20220830 (https://download.01.org/0day-ci/archive/20220831/202208311418.jkohaAzL-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 1c66bacd6cde1f37d6ac96c45b389666a1334ec0)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/63f3651a67a805e471d31f4dc870dd65ddeaacce
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Suren-Baghdasaryan/Code-tagging-framework-and-applications/20220831-055155
git checkout 63f3651a67a805e471d31f4dc870dd65ddeaacce
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> lib/string.c:607: warning: expecting prototype for strsep_no_empt(). Prototype was for strsep_no_empty() instead
vim +607 lib/string.c
598
599 /**
600 * strsep_no_empt - Split a string into tokens, but don't return empty tokens
601 * @s: The string to be searched
602 * @ct: The characters to search for
603 *
604 * strsep() updates @s to point after the token, ready for the next call.
605 */
606 char *strsep_no_empty(char **s, const char *ct)
> 607 {
608 char *ret;
609
610 do {
611 ret = strsep(s, ct);
612 } while (ret && !*ret);
613
614 return ret;
615 }
616 EXPORT_SYMBOL_GPL(strsep_no_empty);
617
--
0-DAY CI Kernel Test Service
https://01.org/lkp
parent reply other threads:[~2022-08-31 6:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220830214919.53220-18-surenb@google.com>]
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=202208311418.jkohaAzL-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
--cc=surenb@google.com \
/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