From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48428) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7OrP-00033B-L4 for qemu-devel@nongnu.org; Tue, 23 Jun 2015 10:07:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7OrL-0000z4-KP for qemu-devel@nongnu.org; Tue, 23 Jun 2015 10:07:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35649) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7OrL-0000yr-Fe for qemu-devel@nongnu.org; Tue, 23 Jun 2015 10:07:31 -0400 Date: Tue, 23 Jun 2015 16:07:29 +0200 From: "Michael S. Tsirkin" Message-ID: <20150623155722-mutt-send-email-mst@redhat.com> References: <20150428162442-mutt-send-email-mst@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150428162442-mutt-send-email-mst@redhat.com> Subject: [Qemu-devel] registering QEMU ACPI ID List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Peter Maydell Hello! QEMU uses the ACPI Vendor ID "QEMU" in some of the ACPI tables it generates. This is a bit of a spec violation: all IDs must be registered with the ASWG. >>From the ASWG point of view, things are easier if a legal entity owns a vendor ID, so Red Hat could ask to own the ID on behalf of the community. I intend to ask the ASWG to register this ID for Red Hat 2 weeks from now, July 7th. If anyone has questions or concerns, please speak now. Thanks! -- MST