qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: anthony.perard@citrix.com, jasowang@redhat.com,
	qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PULL] pci, virtio, net
Date: Thu, 5 Apr 2012 15:03:49 +0300	[thread overview]
Message-ID: <20120405120348.GA31982@redhat.com> (raw)
In-Reply-To: <4F6776C4.8070601@codemonkey.ws>

On Mon, Mar 19, 2012 at 01:11:16PM -0500, Anthony Liguori wrote:
> On 03/15/2012 06:49 PM, Michael S. Tsirkin wrote:
> >I'm trying a signed pull request now. You can check the signature
> >on for_anthony if you like, and if your git is recent enough
> >it will do it for you automatically.
> >
> >The following changes since commit ae7d54d489540b49b7c13a7df7ddc220588a2ced:
> >
> >   target-lm32/microblaze: Drop second CPU{LM32, MB}State typedef (2012-03-14 19:48:37 -0500)
> >
> >are available in the git repository at:
> >
> >   git://github.com/mstsirkin/qemu.git for_anthony
> 
> Pulled.  Thanks.
> 
> Regards,
> 
> Anthony Liguori
> >
> >for you to fetch changes up to ff71f2e8cacefae99179993204172bc65e4303df:
> >
> >   rtl8139: do the network/host communication only in normal operating mode (2012-03-16 01:04:51 +0200)

A lot of time passed and the master still does not appear
to be updated with these patches:

$ git fetch -v origin
>From git://git.qemu.org/qemu
 = [up to date]      master     -> origin/master
 = [up to date]      stable-0.10 -> origin/stable-0.10
 = [up to date]      stable-0.11 -> origin/stable-0.11
 = [up to date]      stable-0.12 -> origin/stable-0.12
 = [up to date]      stable-0.13 -> origin/stable-0.13
 = [up to date]      stable-0.14 -> origin/stable-0.14
 = [up to date]      stable-0.15 -> origin/stable-0.15
 = [up to date]      stable-1.0 -> origin/stable-1.0
 = [up to date]      staging    -> origin/staging
$ git log  --oneline
origin/master..ff71f2e8cacefae99179993204172bc65e4303df|wc -l
21

Is something wrong?
Also, staging is out-of-date, isn't it?
It would be nice to push it once in a while too.

> >
> >----------------------------------------------------------------
> >pci, virtio, net
> >
> >This includes a new standard pci bridge device,
> >as well as a collection of misc fixes for
> >pci, virito and rtl8139.
> >
> >Signed-off-by: Michael S. Tsirkin<mst@redhat.com>
> >
> >----------------------------------------------------------------
> >Anthony PERARD (3):
> >       pci: Do not check if a bus exist in pci_parse_devaddr.
> >       pci_regs: Fix value of PCI_EXP_TYPE_RC_EC.
> >       pci_regs: Add PCI_EXP_TYPE_PCIE_BRIDGE
> >
> >Jason Wang (6):
> >       rtl8139: limit transmission buffer size in c+ mode
> >       rtl8139: remove unused marco
> >       rtl8139: support byte read to TxStatus registers
> >       net: move compute_mcast_idx() to net.h
> >       rtl8139: correctly check the opmode
> >       rtl8139: do the network/host communication only in normal operating mode
> >
> >Michael S. Tsirkin (12):
> >       pci_bridge: fix status: do not override cap bit
> >       pci: don't export an internal function
> >       pci: make another unused extern function static
> >       pci_bridge: user-friendly default bus name
> >       shpc: standard hot plug controller
> >       slotid: add slot id capability
> >       pci: add standard bridge device
> >       pci: set memory type for memory behind the bridge
> >       pcie: drop functionality moved to core
> >       pci: fix bridge IO/BASE
> >       pci_bridge: upper 32 bit are long registers
> >       virtio-net: add DATA_VALID flag
> >
> >  Makefile.objs       |    4 +-
> >  hw/eepro100.c       |   25 --
> >  hw/ne2000.c         |   24 --
> >  hw/opencores_eth.c  |   25 --
> >  hw/pci.c            |   28 +-
> >  hw/pci.h            |   11 +-
> >  hw/pci_bridge.c     |   22 ++-
> >  hw/pci_bridge_dev.c |  174 +++++++++++++
> >  hw/pci_regs.h       |    3 +-
> >  hw/pcie_port.c      |   12 +-
> >  hw/rtl8139.c        |   88 ++++---
> >  hw/shpc.c           |  681 +++++++++++++++++++++++++++++++++++++++++++++++++++
> >  hw/shpc.h           |   48 ++++
> >  hw/slotid_cap.c     |   44 ++++
> >  hw/slotid_cap.h     |   11 +
> >  hw/virtio-net.h     |    1 +
> >  net.c               |   23 ++
> >  net.h               |    3 +
> >  qemu-common.h       |    1 +
> >  19 files changed, 1078 insertions(+), 150 deletions(-)
> >  create mode 100644 hw/pci_bridge_dev.c
> >  create mode 100644 hw/shpc.c
> >  create mode 100644 hw/shpc.h
> >  create mode 100644 hw/slotid_cap.c
> >  create mode 100644 hw/slotid_cap.h
> >
> >

  parent reply	other threads:[~2012-04-05 12:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 23:49 [Qemu-devel] [PULL] pci, virtio, net Michael S. Tsirkin
2012-03-16 18:21 ` Anthony Liguori
2012-03-19 18:11 ` Anthony Liguori
2012-04-03 14:41   ` Michael S. Tsirkin
2012-04-05 12:03   ` Michael S. Tsirkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-01 14:27 Michael S. Tsirkin
2011-08-03  8:15 ` Markus Armbruster
2011-08-03  8:19   ` Michael S. Tsirkin
2011-08-04 21:45     ` Anthony Liguori
2011-08-04 22:44 ` Anthony Liguori

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=20120405120348.GA31982@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony.perard@citrix.com \
    --cc=anthony@codemonkey.ws \
    --cc=jasowang@redhat.com \
    --cc=kraxel@redhat.com \
    --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).