From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "jbaron@redhat.com" <jbaron@redhat.com>,
"fernando@oss.ntt.co.jp" <fernando@oss.ntt.co.jp>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
"kakuta.hayato@oss.ntt.co.jp" <kakuta.hayato@oss.ntt.co.jp>
Subject: Re: [Qemu-devel] [PULL] rtl8139,pci,msi
Date: Mon, 11 Jun 2012 23:01:09 +0300 [thread overview]
Message-ID: <20120611200109.GA10228@redhat.com> (raw)
In-Reply-To: <4FD6296D.4070608@siemens.com>
On Mon, Jun 11, 2012 at 07:22:53PM +0200, Jan Kiszka wrote:
> On 2012-06-11 19:16, Anthony Liguori wrote:
> > On 06/07/2012 11:38 AM, Michael S. Tsirkin wrote:
> >> The following changes since commit 8cc9b43f7c5f826b39af4b012ad89bb55faac29c:
> >>
> >> target-microblaze: lwx/swx: first implementation (2012-06-04 10:19:46 +0200)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_anthony
> >>
> >> for you to fetch changes up to 11e02c393109508fde4d99650f003dd2d6029bc5:
> >>
> >> pci_bridge_dev: fix error path in pci_bridge_dev_initfn() (2012-06-07 17:19:01 +0300)
> >>
> >> ----------------------------------------------------------------
> >> rtl8139,pci,msi
> >>
> >> This pull includes a bugfix for rtl8139 (this is independent of
> >> Jason Wang's fix which Anthony has merged) and pci bridge hotplug bugfixes.
> >> Further there are MSI/MSIX fixes and changes by Jan which should
> >> also help merging device assignment down the road.
> >>
> >> Signed-off-by: Michael S. Tsirkin<mst@redhat.com>
> >>
> >> ----------------------------------------------------------------
> >> Fernando Luis Vazquez Cao (1):
> >> rtl8139: honor RxOverflow flag in can_receive method
> >>
> >> Jan Kiszka (9):
> >> ahci: Fix reset of MSI function
> >> intel-hda: Fix reset of MSI function
> >> ahci: Clean up reset functions
> >> msi: Guard msi_reset with msi_present
> >> msi: Invoke msi/msix_reset from PCI core
> >> msi: Guard msi/msix_write_config with msi_present
> >> msi: Invoke msi/msix_write_config from PCI core
> >> msi: Use msi/msix_present more consistently
> >> msix: Drop unused msix_bar_size
> >
> > This last commit made GCC unhappy.
> >
> > CC libhw64/hw/msix.o
> > /home/anthony/git/qemu/hw/msix.c: In function ‘msix_add_config’:
> > /home/anthony/git/qemu/hw/msix.c:58:14: error: variable ‘new_size’ set but not
> > used [-Werror=unused-but-set-variable]
> > cc1: all warnings being treated as errors
>
> Grr, compiler too old to have this.
>
> Please just drop, I'll post a better cleanup in another round.
>
> Jan
I pushed a fixed for_anthony tag but didn't have time to test yet.
> --
> Siemens AG, Corporate Technology, CT T DE IT 1
> Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-06-11 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 16:38 [Qemu-devel] [PULL] rtl8139,pci,msi Michael S. Tsirkin
2012-06-11 17:16 ` Anthony Liguori
2012-06-11 17:22 ` Jan Kiszka
2012-06-11 20:01 ` Michael S. Tsirkin [this message]
2012-06-11 18:07 ` 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=20120611200109.GA10228@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=fernando@oss.ntt.co.jp \
--cc=jan.kiszka@siemens.com \
--cc=jbaron@redhat.com \
--cc=kakuta.hayato@oss.ntt.co.jp \
--cc=qemu-devel@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).