From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-efi@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-kernel@vger.kernel.org,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kweh Hock Leong <hock.leong.kweh@intel.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: [GIT PULL 0/2] EFI updates for v4.15
Date: Wed, 25 Oct 2017 11:14:17 +0100 [thread overview]
Message-ID: <20171025101419.26369-1-ard.biesheuvel@linaro.org> (raw)
The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git efi-next
for you to fetch changes up to c19611def8fd3f524bc945f0e8f9becace8fdf06:
arm64: efi: ignore EFI_MEMORY_XP attribute if RP and/or WP are set (2017-10-16 16:21:26 +0100)
----------------------------------------------------------------
EFI changes for v4.15:
- ignore EFI_MEMORY_XP attributes on ARM if _RP/_WP are set as well
- a cosmetic pr_err() format string fix
----------------------------------------------------------------
Ard Biesheuvel (1):
arm64: efi: ignore EFI_MEMORY_XP attribute if RP and/or WP are set
Arvind Yadav (1):
efi/capsule-loader: pr_err() strings should end with newlines
arch/arm64/kernel/efi.c | 4 +++-
drivers/firmware/efi/capsule-loader.c | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2017-10-25 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 10:14 Ard Biesheuvel [this message]
2017-10-25 10:14 ` [PATCH 1/2] efi/capsule-loader: pr_err() strings should end with newlines Ard Biesheuvel
2017-10-25 10:14 ` [PATCH 2/2] arm64: efi: ignore EFI_MEMORY_XP attribute if RP and/or WP are set Ard Biesheuvel
2017-12-26 10:40 ` [GIT PULL 0/2] EFI updates for v4.15 Ard Biesheuvel
2017-12-27 18:46 ` Ingo Molnar
2017-12-28 22:20 ` Ard Biesheuvel
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=20171025101419.26369-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=arvind.yadav.cs@gmail.com \
--cc=hock.leong.kweh@intel.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
/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®