All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: kbuild-all-JC7UmRfGjtg@public.gmane.org,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [efi:next 11/13] drivers/firmware/efi/libstub/efi-stub-helper.c:421:40: error: 'CONFIG_CMDLINE' undeclared
Date: Tue, 28 Mar 2017 00:02:02 +0800	[thread overview]
Message-ID: <201703280049.3x17SUu2%fengguang.wu@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
head:   d1dd38ec76a7b1be8f6d0861e149c1d52b784af4
commit: 187fdd765fd12cad29a80d084002e18e643a4d97 [11/13] efi/libstub: unify command line param parsing
config: x86_64-randconfig-x012-201713 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        git checkout 187fdd765fd12cad29a80d084002e18e643a4d97
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/firmware/efi/libstub/efi-stub-helper.c: In function 'efi_parse_options':
>> drivers/firmware/efi/libstub/efi-stub-helper.c:421:40: error: 'CONFIG_CMDLINE' undeclared (first use in this function)
     static const char default_cmdline[] = CONFIG_CMDLINE;
                                           ^~~~~~~~~~~~~~
   drivers/firmware/efi/libstub/efi-stub-helper.c:421:40: note: each undeclared identifier is reported only once for each function it appears in

vim +/CONFIG_CMDLINE +421 drivers/firmware/efi/libstub/efi-stub-helper.c

   415	 * It should be noted that efi= is parsed in two very different
   416	 * environments, first in the early boot environment of the EFI boot
   417	 * stub, and subsequently during the kernel boot.
   418	 */
   419	efi_status_t efi_parse_options(char const *cmdline)
   420	{
 > 421		static const char default_cmdline[] = CONFIG_CMDLINE;
   422		char *str;
   423	
   424		if (IS_ENABLED(CONFIG_CMDLINE_FORCE))

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

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

                 reply	other threads:[~2017-03-27 16:02 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=201703280049.3x17SUu2%fengguang.wu@intel.com \
    --to=fengguang.wu-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.