qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: aik@ozlabs.ru, jan.kiszka@siemens.com,
	alex.williamson@redhat.com, qemu-devel@nongnu.org,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PULL] pci,msi,virtio
Date: Sun, 29 Jul 2012 17:21:14 +0300	[thread overview]
Message-ID: <20120729142114.GB14278@redhat.com> (raw)
In-Reply-To: <500D7755.90407@suse.de>

On Mon, Jul 23, 2012 at 06:09:57PM +0200, Andreas Färber wrote:
> Am 19.07.2012 17:15, schrieb Michael S. Tsirkin:
> > The following changes since commit 80aa796bf38b7ef21daa42673b4711510c450d8a:
> > 
> >   pci_bridge_dev: fix error path in pci_bridge_dev_initfn() (2012-06-11 22:55:13 +0300)
> > 
> > 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 932d4a42afa28829fadf3cbfbb0507cc09aafd8b:
> > 
> >   msi/msix: added API to set MSI message address and data (2012-07-19 17:56:42 +0300)
> > 
> > ----------------------------------------------------------------
> > pci,msi,virtio
> > 
> > This pull includes preparation patches mostly by Jan and Alex
> > that should help merge device assignment down the road.
> > And there's a new API needed for emulating POWER firmware.
> > 
> > So no new functionality and some unused APIs but it looks like
> > merging will help people make progress.
> > 
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> 
> Usually, PULLs are expected to carry the individual patches as replies.
> 
> But more important, did something go wrong with rebasing before sending
> out the PULL? June 11 is more than a month ago. And if I try to rebase
> my pci_host branch on your "pci" branch it tries to replay loads of
> really old post-1.1 commits (e.g., my "Pass PowerPCCPU to...") and
> fails... am I doing something wrong? "for_anthony" tag and "pci" branch
> seem to match in date at least.
> 
> Regards,
> Andreas

I am guessing you mixed up upstream and onto options for git rebase,
happens to me a lot.

Should be something like

git rebase --onto pci origin/master


> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
> 

      parent reply	other threads:[~2012-07-29 14:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 15:15 [Qemu-devel] [PULL] pci,msi,virtio Michael S. Tsirkin
2012-07-23 16:09 ` Andreas Färber
2012-07-23 16:39   ` Anthony Liguori
2012-07-23 16:47     ` Andreas Färber
2012-07-23 17:05     ` Alex Williamson
2012-07-23 18:16       ` Anthony Liguori
2012-07-23 18:29         ` Alex Williamson
2012-07-24 11:32           ` Andreas Färber
2012-07-25  1:56             ` Alexey Kardashevskiy
2012-07-25  9:16               ` Andreas Färber
2012-07-29 13:58       ` Michael S. Tsirkin
2012-07-29 14:17     ` Michael S. Tsirkin
2012-07-29 14:21   ` Michael S. Tsirkin [this message]

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=20120729142114.GB14278@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.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).