public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Kiper <daniel.kiper@oracle.com>
To: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, stable@vger.kernel.org,
	xen-devel@lists.xenproject.org
Cc: boris.ostrovsky@oracle.com, jgross@suse.com, tglx@linutronix.de,
	mingo@redhat.com, hpa@zytor.com, matt@codeblueprint.co.uk,
	ard.biesheuvel@linaro.org
Subject: [PATCH 0/2] xen/efi: Fixes
Date: Tue, 20 Jun 2017 22:14:26 +0200	[thread overview]
Message-ID: <1497989668-6238-1-git-send-email-daniel.kiper@oracle.com> (raw)

Hey,

Two small fixes for Xen dom0 running on x86_64 EFI platforms.

I am CC-ing stable maintainers because similar stuff is needed for various
stable kernels too. Unfortunately, almost every version needs a bit different
set of fixes. So, please treat this email more as head up than real set of
patches for your kernel. If you wish to get Xen EFI stuff fixed just drop me
a line. Then I will prepare set of patches for your kernel (if needed).

Daniel

 arch/x86/xen/efi.c         |   45 ++++++++++++---------------------------------
 drivers/firmware/efi/efi.c |    3 ++-
 2 files changed, 14 insertions(+), 34 deletions(-)

Daniel Kiper (2):
      efi: Process MEMATTR table only if EFI_MEMMAP
      x86/xen/efi: Init only efi struct members used by Xen

             reply	other threads:[~2017-06-20 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 20:14 Daniel Kiper [this message]
2017-06-20 20:14 ` [PATCH 1/2] efi: Process MEMATTR table only if EFI_MEMMAP Daniel Kiper
2017-06-21  7:48   ` Ard Biesheuvel
2017-06-20 20:14 ` [PATCH 2/2] x86/xen/efi: Init only efi struct members used by Xen Daniel Kiper
2017-06-21  7:53   ` Ard Biesheuvel
2017-06-21  8:10   ` [Xen-devel] " Andrew Cooper
2017-06-21  9:29     ` Daniel Kiper
2017-06-21  9:24   ` Ingo Molnar
2017-06-21  9:32     ` Daniel Kiper

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=1497989668-6238-1-git-send-email-daniel.kiper@oracle.com \
    --to=daniel.kiper@oracle.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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