From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NzQIj-0001of-3l for qemu-devel@nongnu.org; Wed, 07 Apr 2010 04:07:53 -0400 Received: from [140.186.70.92] (port=42730 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NzQIf-0001n4-98 for qemu-devel@nongnu.org; Wed, 07 Apr 2010 04:07:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NzQIb-00084F-KI for qemu-devel@nongnu.org; Wed, 07 Apr 2010 04:07:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51067) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NzQIb-000848-Cq for qemu-devel@nongnu.org; Wed, 07 Apr 2010 04:07:45 -0400 Date: Wed, 7 Apr 2010 11:04:01 +0300 From: "Michael S. Tsirkin" Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] [PATCH 0/2] pci_add_capability_at_offset List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: weil@mail.berlios.de, qemu-devel@nongnu.org eepro100 has to jump through hoops to add capability at a specific offset. It's cleaner to simply add an API for that. Michael S. Tsirkin (2): pci: add API to add capability at a known offset eepro100: convert to new capability API hw/eepro100.c | 22 +++++++++------------- hw/pci.c | 16 ++++++++++++---- hw/pci.h | 2 ++ 3 files changed, 23 insertions(+), 17 deletions(-)