mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: kbuild-all@01.org, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@suse.de>,
	Joerg Roedel <jroedel@suse.de>, Dave Young <dyoung@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jiri Kosina <jkosina@suse.cz>, Baoquan He <bhe@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Mark Salter <msalter@redhat.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Alexander Kuleshov <kuleshovmail@gmail.com>
Subject: Re: [PATCH v3] x86/setup: get ramdisk parameters only once
Date: Tue, 9 Feb 2016 21:22:47 +0800	[thread overview]
Message-ID: <201602092108.QIFRjzAb%fengguang.wu@intel.com> (raw)
In-Reply-To: <1455022488-1519-1-git-send-email-kuleshovmail@gmail.com>

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

Hi Alexander,

[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.5-rc3 next-20160209]
[cannot apply to tip/auto-latest]
[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/Alexander-Kuleshov/x86-setup-get-ramdisk-parameters-only-once/20160209-210207
config: i386-alldefconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   arch/x86/kernel/setup.c: In function 'setup_arch':
>> arch/x86/kernel/setup.c:839:12: error: implicit declaration of function 'get_ramdisk_image' [-Werror=implicit-function-declaration]
      .image = get_ramdisk_image(),
               ^
>> arch/x86/kernel/setup.c:840:12: error: implicit declaration of function 'get_ramdisk_size' [-Werror=implicit-function-declaration]
      .size  = get_ramdisk_size(),
               ^
   cc1: some warnings being treated as errors

vim +/get_ramdisk_image +839 arch/x86/kernel/setup.c

   833	 *
   834	 * Note: On x86_64, fixmaps are ready for use even before this is called.
   835	 */
   836	void __init setup_arch(char **cmdline_p)
   837	{
   838		struct ramdisk ramdisk_image = {
 > 839			.image = get_ramdisk_image(),
 > 840			.size  = get_ramdisk_size(),
   841			/* Assume only end is not page aligned */
   842			.end = PAGE_ALIGN(ramdisk_image.image + ramdisk_image.size)
   843		};

---
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: 9683 bytes --]

      parent reply	other threads:[~2016-02-09 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 12:54 Alexander Kuleshov
2016-02-09 13:13 ` Ingo Molnar
2016-02-09 13:22 ` kbuild 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=201602092108.QIFRjzAb%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bp@suse.de \
    --cc=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jkosina@suse.cz \
    --cc=jroedel@suse.de \
    --cc=kbuild-all@01.org \
    --cc=kuleshovmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=msalter@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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®