Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1591810 > unrolled thread
| Started by | Borislav Petkov <bp@alien8.de> |
|---|---|
| First post | 2017-03-03 11:00 +0100 |
| Last post | 2017-03-03 11:00 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC PATCH v4 11/28] x86: Add support to determine the E820 type of an address Borislav Petkov <bp@alien8.de> - 2017-03-03 11:00 +0100
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Date | 2017-03-03 11:00 +0100 |
| Subject | Re: [RFC PATCH v4 11/28] x86: Add support to determine the E820 type of an address |
| Message-ID | <tgSae-7JR-7@gated-at.bofh.it> |
On Tue, Feb 28, 2017 at 04:34:39PM -0600, Tom Lendacky wrote:
> Or if we want to guard against ACPI adding a type 0 in the future, I
> could make the function return an int and then return -EINVAL if an e820
> entry isn't found. This might be the better option.
Yap, think so too. I don't trust specs anyway :)
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Back to top | Article view | linux.kernel
csiph-web