From: "Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>
To: lkp <lkp@intel.com>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
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>,
"Neri, Ricardo" <ricardo.neri@intel.com>,
"Shankar, Ravi V" <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 07:18:28 +0000 [thread overview]
Message-ID: <FFF73D592F13FD46B8700F0A279B802F45FD1614@ORSMSX111.amr.corp.intel.com> (raw)
In-Reply-To: <201806261053.B3CmI5Dm%fengguang.wu@intel.com>
>
> 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
[1] https://lkml.org/lkml/2018/6/22/39
Regards,
Sai
next prev parent reply other threads:[~2018-06-26 7:18 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
2018-06-26 3:15 ` kbuild test robot
2018-06-26 7:18 ` Prakhya, Sai Praneeth [this message]
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=FFF73D592F13FD46B8700F0A279B802F45FD1614@ORSMSX111.amr.corp.intel.com \
--to=sai.praneeth.prakhya@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 \
/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®