| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAFEAcA-HZVJCa44g0-emN06-_a1DgsjtT4cC2_BBQgEyz-=akw@mail.gmail.com> Date: Wed, 29 Jul 2015 18:52:29 +0100 From: Peter Maydell <peter.maydell@...aro.org> To: G Gregory <graeme.gregory@...aro.org> Cc: "Michael S. Tsirkin" <mst@...hat.com>, "virtualization@...ts.linux-foundation.org" <virtualization@...ts.linux-foundation.org>, lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>, Shannon Zhao <shannon.zhao@...aro.org>, Alex Bennée <alex.bennee@...aro.org> Subject: Re: [PATCH] virtio_mmio: add ACPI probing On 28 July 2015 at 11:33, G Gregory <graeme.gregory@...aro.org> 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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists