mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Daniel Baluta <daniel.baluta@intel.com>
Cc: kbuild-all@01.org, matt@codeblueprint.co.uk,
	linux-efi@vger.kernel.org, stefan.stanacar@intel.com,
	octavian.purdila@intel.com, daniel.baluta@intel.com,
	linux-kernel@vger.kernel.org, matthew.k.gumbel@intel.com,
	mohamed.abbas@intel.com, constantin.musca@intel.com
Subject: Re: [PATCH v2] efi: Introduce EFI bootloader control driver
Date: Fri, 18 Mar 2016 20:46:15 +0800	[thread overview]
Message-ID: <201603182033.OXUrE2TX%fengguang.wu@intel.com> (raw)
In-Reply-To: <1458295910-26557-1-git-send-email-daniel.baluta@intel.com>

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

Hi Matt,

[auto build test WARNING on efi/next]
[also build test WARNING on v4.5 next-20160318]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Daniel-Baluta/efi-Introduce-EFI-bootloader-control-driver/20160318-181048
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git next
config: i386-allyesconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   drivers/firmware/efi/efi-bc.c: In function 'efibc_reboot_notifier_call':
>> drivers/firmware/efi/efi-bc.c:93:10: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'size_t {aka unsigned int}' [-Wformat=]
   drivers/firmware/efi/efi-bc.c:101:10: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'size_t {aka unsigned int}' [-Wformat=]

vim +93 drivers/firmware/efi/efi-bc.c

    77			goto out;
    78	
    79		name_efichar_blen = efi_char16_bufsz(LOADER_ENTRY_ONE_SHOT);
    80		cmd_efichar_blen = efi_char16_bufsz(cmd);
    81	
    82		name_efichar = kzalloc(name_efichar_blen, GFP_KERNEL);
    83		if (!name_efichar)
    84			goto out;
    85	
    86		cmd_efichar = kzalloc(cmd_efichar_blen, GFP_KERNEL);
    87		if (!cmd_efichar)
    88			goto out;
    89	
    90		if (efichar_from_char(
    91				name_efichar, LOADER_ENTRY_ONE_SHOT, name_efichar_blen)
    92				!= strlen(LOADER_ENTRY_ONE_SHOT)) {
  > 93			pr_err(
    94				"efibc: %s: Failed to convert char to efi_char16_t. length=%lu",
    95				__func__, name_efichar_blen);
    96			goto out;
    97		}
    98	
    99		if (efichar_from_char(cmd_efichar, cmd, cmd_efichar_blen)
   100				!= strlen(cmd)) {
   101			pr_err(

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 52837 bytes --]

  parent reply	other threads:[~2016-03-18 12:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 10:11 Daniel Baluta
2016-03-18 11:22 ` kbuild test robot
2016-03-18 12:46 ` kbuild test robot [this message]
2016-03-18 16:15 ` Matt Fleming
2016-03-18 19:18   ` Stanacar, Stefan
2016-03-24 14:47     ` Matt Fleming
2016-03-24 16:15       ` Stanacar, Stefan
2016-03-29 12:53         ` Matt Fleming

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=201603182033.OXUrE2TX%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=constantin.musca@intel.com \
    --cc=daniel.baluta@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=matthew.k.gumbel@intel.com \
    --cc=mohamed.abbas@intel.com \
    --cc=octavian.purdila@intel.com \
    --cc=stefan.stanacar@intel.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

all inboxes | Powered by JetHome®