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 v2 4/5] efi: implement generic support for the Memory Attributes table
Date: Wed, 13 Apr 2016 11:24:08 +0100	[thread overview]
Message-ID: <20160413102408.GL2829@codeblueprint.co.uk> (raw)
In-Reply-To: <CAKv+Gu-bLN16YKei3togReQBNo+ScQVf7ek2NJEZAEyii2JEcw@mail.gmail.com>

On Wed, 13 Apr, at 10:29:23AM, Ard Biesheuvel wrote:
> 
> I think it is implied by the spec that this table and the one returned
> by GetMemoryMap() use mutually compatible definitions of
> EFI_MEMORY_DESCRIPTOR. However, since our definition of the struct
> type is based on version 1, we should perhaps add a check for that
> separately

That makes sense. Could you send a patch for that on top of 'next'
(I've dropped the desc_size check now)?

  reply	other threads:[~2016-04-13 10:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 16:38 [PATCH v2 0/5] UEFI: memory attribute table support Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 1/5] ARM: efi: apply strict permissons for UEFI Runtime Services regions Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 2/5] arm64: " Ard Biesheuvel
2016-05-18  0:40   ` Shanker Donthineni
2016-05-18  6:18     ` Ard Biesheuvel
2016-05-18 13:06       ` Shanker Donthineni
2016-05-18 13:08         ` Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 3/5] efi: add support for the EFI_MEMORY_ATTRIBUTES_TABLE config table Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 4/5] efi: implement generic support for the Memory Attributes table Ard Biesheuvel
2016-04-01 12:36   ` Ard Biesheuvel
2016-04-08 15:56   ` Matt Fleming
2016-04-11 14:09     ` Ard Biesheuvel
2016-04-12 19:57       ` Matt Fleming
2016-04-13  8:29         ` Ard Biesheuvel
2016-04-13 10:24           ` Matt Fleming [this message]
2016-04-13 10:24             ` Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 5/5] arm*: efi: take the Memory Attributes table into account 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=20160413102408.GL2829@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).