public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: Dimitrije Pavlov <Dimitrije.Pavlov@arm.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	 Leif Lindholm <quic_llindhol@quicinc.com>,
	Graeme Gregory <graeme@nuviainc.com>,
	 Radoslaw Biernacki <rad@semihalf.com>,
	Jeff Booher-Kaeding <Jeff.Booher-Kaeding@arm.com>,
	 Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
	Sunny Wang <Sunny.Wang@arm.com>,
	 Jeremy Linton <Jeremy.Linton@arm.com>
Subject: Re: [edk2-platforms][PATCH v1 1/1] Silicon/Qemu: Provide _STA ACPI method
Date: Tue, 28 Jun 2022 19:25:56 +0200	[thread overview]
Message-ID: <CAMj1kXF3yXSdsdqDGXzrXOEX=E_YgXTnmKgDXPRcGTaAj7bsag@mail.gmail.com> (raw)
In-Reply-To: <20220628162611.6252-1-Dimitrije.Pavlov@arm.com>

On Tue, 28 Jun 2022 at 18:26, Dimitrije Pavlov <Dimitrije.Pavlov@arm.com> wrote:
>
> SBBR requires platforms to provide the _STA ACPI method for each
> defined device. This patch implements a stub method that always
> indicates devices are present and functional.
>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
> Cc: Graeme Gregory <graeme@nuviainc.com>
> Cc: Radoslaw Biernacki <rad@semihalf.com>
> Cc: Jeff Booher-Kaeding <Jeff.Booher-Kaeding@arm.com>
> Cc: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
> Cc: Sunny Wang <Sunny.Wang@arm.com>
> Cc: Jeremy Linton <Jeremy.Linton@arm.com>
>
> Signed-off-by: Dimitrije Pavlov <Dimitrije.Pavlov@arm.com>

For the record, I will mention again that I think it is a stupid idea
to *require* that every object has a _STA method that behaves exactly
the same as having no _STA at all. Oh well ...

Pushed as f653a22385f5..8e067b431294

      reply	other threads:[~2022-06-28 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 16:26 [edk2-platforms][PATCH v1 1/1] Silicon/Qemu: Provide _STA ACPI method Dimitrije Pavlov
2022-06-28 17:25 ` Ard Biesheuvel [this message]

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='CAMj1kXF3yXSdsdqDGXzrXOEX=E_YgXTnmKgDXPRcGTaAj7bsag@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