Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753966AbbG2Rwv (ORCPT ); Wed, 29 Jul 2015 13:52:51 -0400 Received: from mail-vn0-f54.google.com ([209.85.216.54]:32887 "EHLO mail-vn0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752532AbbG2Rwt (ORCPT ); Wed, 29 Jul 2015 13:52:49 -0400 MIME-Version: 1.0 In-Reply-To: References: <1438076642-12080-1-git-send-email-graeme.gregory@linaro.org> <20150728130604-mutt-send-email-mst@redhat.com> <20150728132113-mutt-send-email-mst@redhat.com> From: Peter Maydell Date: Wed, 29 Jul 2015 18:52:29 +0100 Message-ID: Subject: Re: [PATCH] virtio_mmio: add ACPI probing To: G Gregory Cc: "Michael S. Tsirkin" , "virtualization@lists.linux-foundation.org" , lkml - Kernel Mailing List , Shannon Zhao , =?UTF-8?B?QWxleCBCZW5uw6ll?= Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 972 Lines: 24 On 28 July 2015 at 11:33, G Gregory wrote: > We assigned LNRO in ASWG to avoid collisions with our prototypes/real > platforms so it makes sense to me to switch to QEMUXXXX. So just to check, if we switch virtio-mmio from an LNRO0005 ID to a QEMUxxxx ID we aren't going to break any existing widely shipped or deployed code, right? If we can change the ID without breaking anything significant then I think the QEMU ID makes more sense; but it doesn't really gain us much beyond tidiness. PS: https://www.kernel.org/doc/Documentation/arm64/arm-acpi.txt uses virtio-mmio and LNRO0005 as its code example, so if we change this then it might be nice to update the docs as a followup. thanks -- PMM -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/