From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels
Date: Fri, 3 Jun 2016 11:00:40 +0100 [thread overview]
Message-ID: <20160603100040.GJ9915@arm.com> (raw)
In-Reply-To: <20160530211212.GG2984@codeblueprint.co.uk>
On Mon, May 30, 2016 at 10:12:12PM +0100, Matt Fleming wrote:
> On Wed, 25 May, at 04:11:56PM, Mark Rutland wrote:
> >
> > No further restriction on alignment is provided in the UEFI
> > specification, neither generically nor in a rule specific to AArch64.
>
> This surprises me. I could have sworn the intention was to add this
> restriction to the spec when the strict permissions were being
> discussed in the UEFI working groups.
>
> Am I reinventing history?
>
> As an aside, Mark, Jeremy, which machines did you see this warning
> triggered on? Preproduction/development boards or also in the wild?
Mark, Jeremy?
I've kept this patch marked as unread, but it's not clear to me (a) how
urgent it is (b) what tree it should go through and (c) whether it's the
right thing to do!
Will
next prev parent reply other threads:[~2016-06-03 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 15:11 [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels Mark Rutland
2016-05-25 15:23 ` Ard Biesheuvel
2016-05-25 16:12 ` Mark Rutland
2016-05-25 18:23 ` Ard Biesheuvel
2016-05-26 10:56 ` Mark Rutland
2016-06-03 15:50 ` Ard Biesheuvel
2016-05-25 15:31 ` Catalin Marinas
2016-05-25 15:38 ` Jeremy Linton
2016-05-30 21:12 ` Matt Fleming
2016-06-03 10:00 ` Will Deacon [this message]
2016-06-17 21:16 ` Matt Fleming
2016-06-23 13:17 ` Mark Rutland
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=20160603100040.GJ9915@arm.com \
--to=will.deacon@arm.com \
--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).