From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-crypto <linux-crypto@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Alexander Graf <graf@amazon.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>, Len Brown <lenb@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/3 v6] ACPI: allow longer device IDs
Date: Mon, 28 Feb 2022 22:54:39 +0100 [thread overview]
Message-ID: <CAHmME9qW4EiYU6_kTffMdK5ijJY1DF6YRt=gDjj1vKqDxB0Raw@mail.gmail.com> (raw)
In-Reply-To: <Yh0+LA8B1jw8tnl9@smile.fi.intel.com>
Hi Andy,
On Mon, Feb 28, 2022 at 10:28 PM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
> My point is that this is clear abuse of the spec and:
> 1) we have to enable the broken, because it is already in the wild with
> the comment that this is an issue
>
> AND
>
> 2) issue an ECR / work with MS to make sure they understand the problem.
>
> This can be done in parallel. What I meant as a prerequisite is to start doing
> 2) while we have 1) on table.
Oh, okay, that makes sense. If you want to get (2) going, by all means
go for it. I have no idea how to do this myself; Ard said something
about joining the UEFI forum as an individual something or another but
I don't think I'm the man for the job there. Is this something that
Intel can do with their existing membership (is that the right term?)
at the UEFI forum? Or maybe a Microsoft engineer on the list?
From my side, regarding (1), I'm basically just waiting for Rafael's
"Acked-by" (or an explicit nack) so I can put this in my tree and move
on.
Jason
next prev parent reply other threads:[~2022-02-28 21:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 22:06 [PATCH v5 0/3] ACPI: VM fork detection for RNG Jason A. Donenfeld
2022-02-26 22:06 ` [PATCH v5 1/3] random: add mechanism for VM forks to reinitialize crng Jason A. Donenfeld
2022-02-26 22:06 ` [PATCH v5 2/3] ACPI: allow longer device IDs Jason A. Donenfeld
2022-02-27 7:31 ` Ard Biesheuvel
2022-02-27 7:37 ` Ard Biesheuvel
2022-02-27 10:03 ` Jason A. Donenfeld
2022-02-27 10:30 ` Ard Biesheuvel
2022-02-27 10:47 ` Ard Biesheuvel
2022-02-27 11:38 ` Alexander Graf
2022-02-27 11:43 ` Ard Biesheuvel
2022-02-27 11:48 ` Alexander Graf
2022-02-27 11:59 ` Ard Biesheuvel
2022-02-27 11:42 ` Alexander Graf
2022-02-27 12:43 ` Jason A. Donenfeld
2022-02-27 23:27 ` Jason A. Donenfeld
2022-02-28 18:19 ` Rafael J. Wysocki
2022-02-28 18:21 ` Jason A. Donenfeld
2022-02-28 18:33 ` [PATCH 2/3 v6] " Jason A. Donenfeld
2022-02-28 20:46 ` Andy Shevchenko
2022-02-28 20:58 ` Jason A. Donenfeld
2022-02-28 21:02 ` Ard Biesheuvel
2022-02-28 21:27 ` Andy Shevchenko
2022-02-28 21:54 ` Jason A. Donenfeld [this message]
2022-02-28 22:14 ` Michael Kelley (LINUX)
2022-02-28 22:17 ` Jason A. Donenfeld
2022-02-28 22:21 ` Ard Biesheuvel
2022-02-28 22:38 ` Michael Kelley (LINUX)
2022-02-28 22:46 ` Ard Biesheuvel
2022-03-22 19:58 ` Michael Kelley (LINUX)
2022-03-22 20:11 ` Jason A. Donenfeld
2022-03-24 19:25 ` Michael Kelley (LINUX)
2022-03-22 22:06 ` Ard Biesheuvel
2022-03-24 19:24 ` Michael Kelley (LINUX)
2022-03-24 19:45 ` Jason A. Donenfeld
2022-03-24 20:14 ` Michael Kelley (LINUX)
2022-03-01 13:12 ` Andy Shevchenko
2022-02-28 22:00 ` Alexander Graf
2022-02-28 22:17 ` Ard Biesheuvel
2022-03-01 10:35 ` Hans de Goede
2022-03-01 10:38 ` Jason A. Donenfeld
2022-03-01 10:49 ` Hans de Goede
2022-03-01 14:25 ` Andy Shevchenko
2022-03-01 14:48 ` Jason A. Donenfeld
2022-03-01 12:29 ` Rafael J. Wysocki
2022-03-01 10:31 ` [PATCH v5 2/3] " Hans de Goede
2022-02-26 22:06 ` [PATCH v5 3/3] virt: vmgenid: introduce driver for reinitializing RNG on VM fork Jason A. Donenfeld
2022-03-06 16:02 ` Michael Kelley (LINUX)
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='CAHmME9qW4EiYU6_kTffMdK5ijJY1DF6YRt=gDjj1vKqDxB0Raw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=andy.shevchenko@gmail.com \
--cc=ardb@kernel.org \
--cc=graf@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.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).