public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	 Mark Rutland <mark.rutland@arm.com>,
	Drew Jones <drjones@redhat.com>, Jon Masters <jcm@redhat.com>
Subject: Re: [PATCH v2] ArmVirtPkg/PlatformHasAcpiDtDxe: allow guest level ACPI disable override
Date: Thu, 30 Mar 2017 09:40:13 +0100	[thread overview]
Message-ID: <CAKv+Gu8OVQPbPAM1w3yq4FPULkHx_tXxhaUb=EKp+VNxDZOH8A@mail.gmail.com> (raw)
In-Reply-To: <41a87740-7634-bfde-d2fb-3767a5c33140@redhat.com>

On 29 March 2017 at 20:35, Laszlo Ersek <lersek@redhat.com> wrote:
> On 03/29/17 21:10, Ard Biesheuvel wrote:
[...]
>>
>> How on earth is having two ways to disable ACPI rather than one going
>> to cause fragmentation? Unlike v1, this patch does not allow you to
>> expose both DT and ACPI tables at the same time.
>
> Oopsie daisy. You actually updated the commit message too. (I have now
> formally diffed v1 vs. v2, including commit msg -- I generally do that
> when reviewing incremental versions of patches, but it has been a very
> long day, and I failed to get my mind off the track set up by v1). I got
> really no good explanation for missing the fundamental logic change
> between v1 and v2. As you say, version 2 preserves the mutual exclusion
> between DT and ACPI that I'm so annoyingly obsessed about. Thank you for
> the update.
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>

Thanks Laszlo. I am glad we have a solution we can both live with.

I will wait for Marc to confirm that this works as expected for him.

Thanks,
Ard.


  reply	other threads:[~2017-03-30  8:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 17:50 [PATCH v2] ArmVirtPkg/PlatformHasAcpiDtDxe: allow guest level ACPI disable override Ard Biesheuvel
2017-03-29 18:44 ` Laszlo Ersek
2017-03-29 19:10   ` Ard Biesheuvel
2017-03-29 19:35     ` Laszlo Ersek
2017-03-30  8:40       ` Ard Biesheuvel [this message]
2017-03-30 16:16         ` Laszlo Ersek
2017-03-31 10:48           ` Ard Biesheuvel
     [not found]         ` <e3ab9b91-8e0f-52ab-bb3a-53bd0cacf17c@arm.com>
2017-03-31  9:59           ` Laszlo Ersek
2017-03-31 10:10             ` Laszlo Ersek
2017-03-31 10:16             ` Ard Biesheuvel
2017-03-31 10:46               ` Laszlo Ersek
2017-03-31 10:52           ` 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-list 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='CAKv+Gu8OVQPbPAM1w3yq4FPULkHx_tXxhaUb=EKp+VNxDZOH8A@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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