mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
Cc: kbuild-all@01.org, linux-efi@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Sai Praneeth <sai.praneeth.prakhya@intel.com>,
	Lee Chun-Yi <jlee@suse.com>, Borislav Petkov <bp@alien8.de>,
	Dave Young <dyoung@redhat.com>, Laszlo Ersek <lersek@redhat.com>,
	Bhupesh Sharma <bhsharma@redhat.com>,
	Ricardo Neri <ricardo.neri@intel.com>,
	Ravi Shankar <ravi.v.shankar@intel.com>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH] efi: Free existing memory map before installing new memory map
Date: Tue, 26 Jun 2018 11:15:23 +0800	[thread overview]
Message-ID: <201806261057.fHkkAzYy%fengguang.wu@intel.com> (raw)
In-Reply-To: <1529980892-11833-1-git-send-email-sai.praneeth.prakhya@intel.com>

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

Hi Sai,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v4.18-rc2 next-20180625]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Sai-Praneeth-Prakhya/efi-Free-existing-memory-map-before-installing-new-memory-map/20180626-104301
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/firmware//efi/memmap.c: In function 'efi_memmap_install':
>> drivers/firmware//efi/memmap.c:199:2: error: implicit declaration of function 'efi_memmap_free'; did you mean 'vmemmap_free'? [-Werror=implicit-function-declaration]
     efi_memmap_free(efi.memmap.phys_map, efi.memmap.nr_map, efi.memmap.late);
     ^~~~~~~~~~~~~~~
     vmemmap_free
   cc1: some warnings being treated as errors

vim +199 drivers/firmware//efi/memmap.c

   180	
   181	/**
   182	 * efi_memmap_install - Install a new EFI memory map in efi.memmap
   183	 * @addr: Physical address of the memory map
   184	 * @nr_map: Number of entries in the memory map
   185	 *
   186	 * Unlike efi_memmap_init_*(), this function does not allow the caller
   187	 * to switch from early to late mappings. It simply uses the existing
   188	 * mapping function and installs the new memmap.
   189	 *
   190	 * Returns zero on success, a negative error code on failure.
   191	 */
   192	int __init efi_memmap_install(phys_addr_t addr, unsigned int nr_map)
   193	{
   194		struct efi_memory_map_data data;
   195	
   196		efi_memmap_unmap();
   197	
   198		/* Free the memory allocated to the existing memory map */
 > 199		efi_memmap_free(efi.memmap.phys_map, efi.memmap.nr_map, efi.memmap.late);
   200	
   201		data.phys_map = addr;
   202		data.size = efi.memmap.desc_size * nr_map;
   203		data.desc_version = efi.memmap.desc_version;
   204		data.desc_size = efi.memmap.desc_size;
   205	
   206		return __efi_memmap_init(&data, efi.memmap.late);
   207	}
   208	

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

  reply	other threads:[~2018-06-26  3:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26  2:41 Sai Praneeth Prakhya
2018-06-26  3:15 ` kbuild test robot [this message]
2018-06-26  3:15 ` kbuild test robot
2018-06-26  7:18   ` Prakhya, Sai Praneeth
2018-06-27  6:02     ` [kbuild-all] " Ye Xiaolong
2018-06-27  6:09       ` Ard Biesheuvel
2018-06-27  6:29         ` Ye Xiaolong
2018-06-27  6:32       ` Prakhya, Sai Praneeth
2018-06-26  9:38 ` Ard Biesheuvel
2018-06-27  4:51   ` Prakhya, Sai Praneeth
2018-06-27  7:01     ` Ard Biesheuvel
2018-06-27  7:28       ` Prakhya, Sai Praneeth

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=201806261057.fHkkAzYy%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bhsharma@redhat.com \
    --cc=bp@alien8.de \
    --cc=dyoung@redhat.com \
    --cc=jlee@suse.com \
    --cc=kbuild-all@01.org \
    --cc=lersek@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=ravi.v.shankar@intel.com \
    --cc=ricardo.neri@intel.com \
    --cc=sai.praneeth.prakhya@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®