From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42489)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1ZmfIr-0001cj-KW
	for qemu-devel@nongnu.org; Thu, 15 Oct 2015 05:58:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1ZmfIl-0005Dm-FV
	for qemu-devel@nongnu.org; Thu, 15 Oct 2015 05:58:29 -0400
Received: from mx1.redhat.com ([209.132.183.28]:51039)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1ZmfIl-0005Db-A8
	for qemu-devel@nongnu.org; Thu, 15 Oct 2015 05:58:23 -0400
Date: Thu, 15 Oct 2015 12:58:18 +0300
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20151015125803-mutt-send-email-mst@redhat.com>
References: <cover.1444835138.git.p.fedin@samsung.com>
	<8ab953090af58ac19d240feb48180b7b6f1f39bb.1444835138.git.p.fedin@samsung.com>
	<20151014190920-mutt-send-email-mst@redhat.com>
	<00c201d10727$2b9921f0$82cb65d0$@samsung.com>
	<20151015120415-mutt-send-email-mst@redhat.com>
	<00d201d1072d$c1be1e00$453a5a00$@samsung.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00d201d1072d$c1be1e00$453a5a00$@samsung.com>
Subject: Re: [Qemu-devel] [PATCH v4 2/3] hw/pci: Introduce pci_requester_id()
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Paolo Bonzini' <pbonzini@redhat.com>, qemu-devel@nongnu.org, 'Peter Maydell' <peter.maydell@linaro.org>

On Thu, Oct 15, 2015 at 12:42:06PM +0300, Pavel Fedin wrote:
>  Hello!
> 
> > Then I realized it's actually the PCI requester ID.
> > That, in turn, means it can just be a generic PCI API,
> > e.g. it's also used for assigning pci-x devices.
> 
>  Ok. So, will it be good if i place it in includes/hw/pci.h as static inline, similar to how it was done in v1?
> 
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia

I think so, yes.