From: Al Stone <ahs3@redhat.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: "kevin.tian@intel.com" <kevin.tian@intel.com>,
"mst@redhat.com" <mst@redhat.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"Boeuf, Sebastien" <sebastien.boeuf@intel.com>,
Alexander Grest <Alexander.Grest@microsoft.com>,
Yinghan Yang <Yinghan.Yang@microsoft.com>
Subject: Re: [EXTERNAL] Re: Question regarding VIOT proposal
Date: Thu, 18 Feb 2021 16:39:43 -0700 [thread overview]
Message-ID: <20210218233943.GH702808@redhat.com> (raw)
In-Reply-To: <YCzj85YDWRxmrCHo@myrica>
On 17 Feb 2021 10:37, Jean-Philippe Brucker wrote:
> On Tue, Feb 16, 2021 at 02:31:03PM -0700, Al Stone wrote:
> > Would you believe last week's meeting was canceled, too? Not sure
> > why the chair/co-chair are doing this but I'm finding it a little
> > frustrating.
> >
> > We'll try again this week ... again, apologies for the delays. I'd
> > recommend going with the last version posted just so progress can be
> > made. The spec can always be fixed later.
>
> Thanks, I'll send the acpica changes for review and follow with QEMU and
> Linux patches. These things also take time so I might as well start in
> parallel.
>
> Thanks,
> Jean
As of today, the proposal has been approved for inclusion in the next
release of the ACPI spec (whatever version gets released post the 6.4
version that just came out).
Congratulations ?!? :)
And thanks to all for their patience during this process. You now
have the dubious disctinction of being the very first table added
to the spec that _started_ as open source.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-02-18 23:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 0:13 Question regarding VIOT proposal Yinghan Yang via iommu
2020-11-05 13:45 ` Jean-Philippe Brucker
2020-11-05 22:05 ` [EXTERNAL] " Yinghan Yang via iommu
2020-11-06 13:57 ` Jean-Philippe Brucker
2020-12-03 22:21 ` Yinghan Yang via iommu
2020-12-03 23:01 ` Al Stone
2020-12-04 18:09 ` Jean-Philippe Brucker
2020-12-04 18:15 ` Yinghan Yang via iommu
2020-12-04 20:18 ` Al Stone
2021-02-02 9:17 ` Jean-Philippe Brucker
2021-02-02 20:27 ` Al Stone
2021-02-03 8:46 ` Jean-Philippe Brucker
2021-02-04 20:25 ` Al Stone
2021-02-16 21:31 ` Al Stone
2021-02-17 9:37 ` Jean-Philippe Brucker
2021-02-18 23:39 ` Al Stone [this message]
2021-02-19 11:24 ` Jean-Philippe Brucker
2021-02-19 17:35 ` Al Stone
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=20210218233943.GH702808@redhat.com \
--to=ahs3@redhat.com \
--cc=Alexander.Grest@microsoft.com \
--cc=Yinghan.Yang@microsoft.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=sebastien.boeuf@intel.com \
/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).