linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: matt@codeblueprint.co.uk (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] efi/arm64: don't apply MEMBLOCK_NOMAP to UEFI memory map mapping
Date: Thu, 31 Mar 2016 21:35:20 +0100	[thread overview]
Message-ID: <20160331203520.GB2736@codeblueprint.co.uk> (raw)
In-Reply-To: <1459323983-9120-1-git-send-email-ard.biesheuvel@linaro.org>

On Wed, 30 Mar, at 09:46:23AM, Ard Biesheuvel wrote:
> Hi Matt,
> 
> Could we queue this as a fix for v4.6 with a cc:stable for v4.5, please?
> (assuming no objections from any of the cc'ees)

Yep, I've picked this up. I'll go out to tip tomorrow.

  parent reply	other threads:[~2016-03-31 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  7:46 [PATCH] efi/arm64: don't apply MEMBLOCK_NOMAP to UEFI memory map mapping Ard Biesheuvel
2016-03-31 10:53 ` Will Deacon
2016-03-31 20:35 ` Matt Fleming [this message]
2016-04-15 16:44   ` Steve Capper
2016-04-15 22:15     ` Matt Fleming
2016-04-16  9:09       ` Ingo Molnar
2016-04-16 10:27         ` Matt Fleming

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=20160331203520.GB2736@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).