All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-4.16-2 tag
Date: Sat, 10 Feb 2018 15:52:32 +0100	[thread overview]
Message-ID: <20180210145231.GA4148@flask> (raw)
In-Reply-To: <20180209094145.GB7725@fergus.ozlabs.ibm.com>

2018-02-09 20:41+1100, Paul Mackerras:
> Paolo or Radim,
> 
> Please do a pull from my kvm-ppc-next-4.16-2 tag to get some PPC KVM
> fixes that I would like to have go into 4.16.  Most of them are quite
> self-contained; there are two that are larger (and arguably don't
> quite count as bug fixes), but I have checked them carefully and
> convinced myself that they have a low risk of causing regressions, and
> they do address issues that have been found in testing, so I put them
> in.
> 
> With things like this I would normally put them in my kvm-ppc-fixes
> branch and base it on current upstream.  However, as far as I can see
> the kvm next branch hasn't been merged upstream yet.  Therefore I made
> this series a continuation of my kvm-ppc-next branch.

I have resolved the resulting conflict and pulled, thanks.

> When do you expect that kvm/next will get merged upstream?

Hopefully on Sunday, sorry for the delay.

WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-4.16-2 tag
Date: Sat, 10 Feb 2018 14:52:32 +0000	[thread overview]
Message-ID: <20180210145231.GA4148@flask> (raw)
In-Reply-To: <20180209094145.GB7725@fergus.ozlabs.ibm.com>

2018-02-09 20:41+1100, Paul Mackerras:
> Paolo or Radim,
> 
> Please do a pull from my kvm-ppc-next-4.16-2 tag to get some PPC KVM
> fixes that I would like to have go into 4.16.  Most of them are quite
> self-contained; there are two that are larger (and arguably don't
> quite count as bug fixes), but I have checked them carefully and
> convinced myself that they have a low risk of causing regressions, and
> they do address issues that have been found in testing, so I put them
> in.
> 
> With things like this I would normally put them in my kvm-ppc-fixes
> branch and base it on current upstream.  However, as far as I can see
> the kvm next branch hasn't been merged upstream yet.  Therefore I made
> this series a continuation of my kvm-ppc-next branch.

I have resolved the resulting conflict and pulled, thanks.

> When do you expect that kvm/next will get merged upstream?

Hopefully on Sunday, sorry for the delay.

  reply	other threads:[~2018-02-10 14:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  9:41 [GIT PULL] Please pull my kvm-ppc-next-4.16-2 tag Paul Mackerras
2018-02-09  9:41 ` Paul Mackerras
2018-02-10 14:52 ` Radim Krčmář [this message]
2018-02-10 14:52   ` Radim Krčmář
  -- strict thread matches above, loose matches on Subject: below --
2018-01-19  4:48 [GIT PULL] Please pull my kvm-ppc-next-4.16-1 tag Paul Mackerras
2018-01-19  4:48 ` Paul Mackerras
2018-02-01 15:17 ` Radim Krčmář
2018-02-01 15:17   ` Radim Krčmář
2018-03-29  5:38 ` [GIT PULL] Please pull my kvm-ppc-next-4.17-1 tag Paul Mackerras
2018-03-29 20:34 ` Radim Krčmář
2018-06-04  1:27 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-1 tag Paul Mackerras
2018-06-13  5:51 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-2 tag Paul Mackerras
2018-06-13 16:22 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-1 tag Paolo Bonzini
2018-06-13 21:52 ` Paul Mackerras
2018-07-31  5:56 ` [GIT PULL] Please pull my kvm-ppc-next-4.19-1 tag Paul Mackerras
2018-08-02 11:56 ` Paolo Bonzini
2018-10-10  5:55 ` [GIT PULL] Please pull my kvm-ppc-next-4.20-1 tag Paul Mackerras
2018-10-10 16:38 ` Paolo Bonzini
2018-10-20 10:53 ` [GIT PULL] Please pull my kvm-ppc-next-4.20-2 tag Paul Mackerras
2018-10-21  9:47 ` Paolo Bonzini
2018-12-18  3:05 ` [GIT PULL] Please pull my kvm-ppc-next-4.21-1 tag Paul Mackerras
2018-12-20 13:58 ` Radim Krčmář
2018-12-21  4:24 ` [GIT PULL] Please pull my kvm-ppc-next-4.21-2 tag Paul Mackerras
2018-12-21 10:48 ` Paolo Bonzini

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=20180210145231.GA4148@flask \
    --to=rkrcmar@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=paulus@ozlabs.org \
    --cc=pbonzini@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.