All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>
Cc: lkp <lkp@intel.com>, "Shankar, Ravi V" <ravi.v.shankar@intel.com>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Laszlo Ersek <lersek@redhat.com>,
	Bhupesh Sharma <bhsharma@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Neri, Ricardo" <ricardo.neri@intel.com>,
	Lee Chun-Yi <jlee@suse.com>, Borislav Petkov <bp@alien8.de>,
	"kbuild-all@01.org" <kbuild-all@01.org>,
	Dave Young <dyoung@redhat.com>
Subject: Re: [kbuild-all] [PATCH] efi: Free existing memory map before installing new memory map
Date: Wed, 27 Jun 2018 14:02:57 +0800	[thread overview]
Message-ID: <20180627060257.GD18756@yexl-desktop> (raw)
In-Reply-To: <FFF73D592F13FD46B8700F0A279B802F45FD1614@ORSMSX111.amr.corp.intel.com>

Hi,

On 06/26, Prakhya, Sai Praneeth wrote:
>> 
>> 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]
>
>Since efi_memmap_free() is a recently introduced API [1], please note that the patch 
>is based on efi tree @https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git

I noticed the official efi tree recored in MAINTAINERS is git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git,
are they identical?

EXTENSIBLE FIRMWARE INTERFACE (EFI)
M:      Matt Fleming <matt@codeblueprint.co.uk>
L:      linux-efi@vger.kernel.org
T:      git git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git
S:      Maintained
F:      Documentation/efi-stub.txt
F:      arch/ia64/kernel/efi.c
F:      arch/x86/boot/compressed/eboot.[ch]
F:      arch/x86/include/asm/efi.h
F:      arch/x86/platform/efi/*
F:      drivers/firmware/efi/*
F:      include/linux/efi*.h


Thanks,
Xiaolong

>
>[1] https://lkml.org/lkml/2018/6/22/39
>
>Regards,
>Sai
>_______________________________________________
>kbuild-all mailing list
>kbuild-all@lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all

  reply	other threads:[~2018-06-27  6:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26  2:41 [PATCH] efi: Free existing memory map before installing new memory map Sai Praneeth Prakhya
2018-06-26  3:15 ` kbuild test robot
2018-06-26  3:15   ` kbuild test robot
2018-06-26  3:15 ` kbuild test robot
2018-06-26  3:15   ` kbuild test robot
2018-06-26  7:18   ` Prakhya, Sai Praneeth
2018-06-27  6:02     ` Ye Xiaolong [this message]
2018-06-27  6:09       ` [kbuild-all] " 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=20180627060257.GD18756@yexl-desktop \
    --to=xiaolong.ye@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=lkp@intel.com \
    --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 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.