From: Gerd Hoffmann <kraxel@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-stable <qemu-stable@nongnu.org>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] pci: fix i82801b11 bridge
Date: Mon, 05 Aug 2013 12:33:14 +0200 [thread overview]
Message-ID: <51FF7F6A.50902@redhat.com> (raw)
In-Reply-To: <51FF7440.1040404@suse.de>
On 08/05/13 11:45, Andreas Färber wrote:
> Am 05.08.2013 10:50, schrieb Gerd Hoffmann:
>> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>> ---
>> hw/pci-bridge/i82801b11.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/hw/pci-bridge/i82801b11.c b/hw/pci-bridge/i82801b11.c
>> index 8a5e426..14cd7fd 100644
>> --- a/hw/pci-bridge/i82801b11.c
>> +++ b/hw/pci-bridge/i82801b11.c
>> @@ -90,6 +90,7 @@ static void i82801b11_bridge_class_init(ObjectClass *klass, void *data)
>> k->device_id = PCI_DEVICE_ID_INTEL_82801BA_11;
>> k->revision = ICH9_D2P_A2_REVISION;
>> k->init = i82801b11_bridge_initfn;
>> + k->config_write = pci_bridge_write_config;
>> set_bit(DEVICE_CATEGORY_BRIDGE, dc->categories);
>> }
>>
>
> We have an abstract TYPE_PCI_BRIDGE now, suggest to set it in its
> class_init instead if that's a generic bridge function.
Well, depends on the bridge device. When they have stuff beside core
pci bridge functionality (such as shpc hotplug support like the
'pci-bridge' device) they need their private function. But those can
still override config_write in the device init I guess.
/me leaves that to mst to decide. Beside that it should most likely go
into a separate cleanup patch as there are other devices which hook
pci_bridge_write_config the same way.
> Probably should be for-1.6?
Yes.
cheers,
Gerd
next prev parent reply other threads:[~2013-08-05 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 8:50 [Qemu-devel] [PATCH] pci: fix i82801b11 bridge Gerd Hoffmann
2013-08-05 9:45 ` Andreas Färber
2013-08-05 10:33 ` Gerd Hoffmann [this message]
2013-08-05 15:39 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51FF7F6A.50902@redhat.com \
--to=kraxel@redhat.com \
--cc=afaerber@suse.de \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).