mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/firmware/efi/libstub/string.c:83:20: warning: no previous prototype for 'simple_strtoull'
Date: Mon, 29 Jun 2020 17:56:40 +0800	[thread overview]
Message-ID: <202006291737.vSJQXxDC%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2588 bytes --]

Hi Ard,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   9ebcfadb0610322ac537dd7aa5d9cbc2b2894c68
commit: 91d150c0cc637b9d9d6394936add7cd2b7ccc410 efi/libstub: Clean up command line parsing routine
date:   4 months ago
config: arm-randconfig-r005-20200629 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
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
        git checkout 91d150c0cc637b9d9d6394936add7cd2b7ccc410
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> drivers/firmware/efi/libstub/string.c:83:20: warning: no previous prototype for 'simple_strtoull' [-Wmissing-prototypes]
      83 | unsigned long long simple_strtoull(const char *cp, char **endp, unsigned int base)
         |                    ^~~~~~~~~~~~~~~
>> drivers/firmware/efi/libstub/string.c:108:6: warning: no previous prototype for 'simple_strtol' [-Wmissing-prototypes]
     108 | long simple_strtol(const char *cp, char **endp, unsigned int base)
         |      ^~~~~~~~~~~~~

vim +/simple_strtoull +83 drivers/firmware/efi/libstub/string.c

    75	
    76	/**
    77	 * simple_strtoull - convert a string to an unsigned long long
    78	 * @cp: The start of the string
    79	 * @endp: A pointer to the end of the parsed string will be placed here
    80	 * @base: The number base to use
    81	 */
    82	
  > 83	unsigned long long simple_strtoull(const char *cp, char **endp, unsigned int base)
    84	{
    85		unsigned long long result = 0;
    86	
    87		if (!base)
    88			base = simple_guess_base(cp);
    89	
    90		if (base == 16 && cp[0] == '0' && TOLOWER(cp[1]) == 'x')
    91			cp += 2;
    92	
    93		while (isxdigit(*cp)) {
    94			unsigned int value;
    95	
    96			value = isdigit(*cp) ? *cp - '0' : TOLOWER(*cp) - 'a' + 10;
    97			if (value >= base)
    98				break;
    99			result = result * base + value;
   100			cp++;
   101		}
   102		if (endp)
   103			*endp = (char *)cp;
   104	
   105		return result;
   106	}
   107	
 > 108	long simple_strtol(const char *cp, char **endp, unsigned int base)

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26221 bytes --]

                 reply	other threads:[~2020-06-29 19:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202006291737.vSJQXxDC%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ardb@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®