From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Brook <paul@codesourcery.com>
Subject: Re: RFC qdev path semantics (was: [Qemu-devel] [RFC PATCH 0/5] Introduce canonical device hierarchy string)
Date: Wed, 16 Jun 2010 11:40:39 +0100
Message-ID: <201006161140.41862.paul@codesourcery.com>
References: <20100614054923.879.33717.stgit@localhost.localdomain> <m3d3vr48f6.fsf@blackfin.pond.sub.org>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Alex Williamson <alex.williamson@redhat.com>,
	qemu-devel@nongnu.org, chrisw@redhat.com, kvm@vger.kernel.org,
	kraxel@redhat.com, avi@redhat.com
To: Markus Armbruster <armbru@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.codesourcery.com ([38.113.113.100]:35076 "EHLO
	mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752821Ab0FPKkt (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 16 Jun 2010 06:40:49 -0400
In-Reply-To: <m3d3vr48f6.fsf@blackfin.pond.sub.org>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

> * Else, use TYPE.NUM, where TYPE is derived from the bus type, and NUM
>   is the bus number, as above.
> 
> ### Paul proposes to either drop TYPE.NUM (and require drivers to
>     provide bus names), or make NUM count separately for each bus type.

I revised this proposal: Drop the .NUM part, and require drivers provide a bus 
name if TYPE would result in ambiguous names.

Paul