From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Ard Biesheuvel
<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Jeremy Linton <jeremy.linton-5wv7dgnIgG8@public.gmane.org>,
Leif Lindholm
<leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels
Date: Mon, 30 May 2016 22:12:12 +0100 [thread overview]
Message-ID: <20160530211212.GG2984@codeblueprint.co.uk> (raw)
In-Reply-To: <1464189116-30898-1-git-send-email-mark.rutland-5wv7dgnIgG8@public.gmane.org>
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?
WARNING: multiple messages have this Message-ID (diff)
From: matt@codeblueprint.co.uk (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/efi: remove spurious WARN_ON for !4K kernels
Date: Mon, 30 May 2016 22:12:12 +0100 [thread overview]
Message-ID: <20160530211212.GG2984@codeblueprint.co.uk> (raw)
In-Reply-To: <1464189116-30898-1-git-send-email-mark.rutland@arm.com>
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?
next prev parent reply other threads:[~2016-05-30 21:12 UTC|newest]
Thread overview: 24+ 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:11 ` Mark Rutland
[not found] ` <1464189116-30898-1-git-send-email-mark.rutland-5wv7dgnIgG8@public.gmane.org>
2016-05-25 15:23 ` Ard Biesheuvel
2016-05-25 15:23 ` Ard Biesheuvel
[not found] ` <BA565A9C-8CC0-42E4-9821-7941852F835A-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-05-25 16:12 ` Mark Rutland
2016-05-25 16:12 ` Mark Rutland
2016-05-25 18:23 ` Ard Biesheuvel
2016-05-25 18:23 ` Ard Biesheuvel
[not found] ` <CAKv+Gu94GLWUJBCtNUDb4Jak3KL0-MGkUfk82fZ5UdwWH60P_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-26 10:56 ` Mark Rutland
2016-05-26 10:56 ` Mark Rutland
2016-06-03 15:50 ` Ard Biesheuvel
2016-06-03 15:50 ` Ard Biesheuvel
2016-05-25 15:31 ` Catalin Marinas
2016-05-25 15:31 ` Catalin Marinas
2016-05-25 15:38 ` Jeremy Linton
2016-05-25 15:38 ` Jeremy Linton
2016-05-30 21:12 ` Matt Fleming [this message]
2016-05-30 21:12 ` Matt Fleming
[not found] ` <20160530211212.GG2984-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-06-03 10:00 ` Will Deacon
2016-06-03 10:00 ` Will Deacon
[not found] ` <20160603100040.GJ9915-5wv7dgnIgG8@public.gmane.org>
2016-06-17 21:16 ` Matt Fleming
2016-06-17 21:16 ` Matt Fleming
[not found] ` <20160617211601.GN2658-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-06-23 13:17 ` Mark Rutland
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=20160530211212.GG2984@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=jeremy.linton-5wv7dgnIgG8@public.gmane.org \
--cc=leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.