From: Paul Mackerras <paulus@ozlabs.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
"Greg Kurz" <groug@kaod.org>,
"Bharata B Rao" <bharata@linux.ibm.com>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.5-2 tag
Date: Mon, 25 Nov 2019 23:44:51 +0000 [thread overview]
Message-ID: <20191125234451.GA11896@blackberry> (raw)
In-Reply-To: <eff48bca-3ef0-8ae4-79d4-5e8087bded1a@redhat.com>
On Mon, Nov 25, 2019 at 11:29:38AM +0100, Paolo Bonzini wrote:
> On 25/11/19 01:58, Paul Mackerras wrote:
>
> Yes, of course (I have even accepted submaintainer pull request for new
> features during the first week of the merge window, so not a problem at
> all).
In that case, I have a patchset from Bharata Rao which is just now
ready to go in. It has been around for a while; Bharata posted v11
yesterday, and we would really like it to go in v5.5, but I thought we
were too late. If you're OK with taking it at this stage then I'll
send you another pull request.
Thanks,
Paul.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@ozlabs.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
"Greg Kurz" <groug@kaod.org>,
"Bharata B Rao" <bharata@linux.ibm.com>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.5-2 tag
Date: Tue, 26 Nov 2019 10:44:51 +1100 [thread overview]
Message-ID: <20191125234451.GA11896@blackberry> (raw)
In-Reply-To: <eff48bca-3ef0-8ae4-79d4-5e8087bded1a@redhat.com>
On Mon, Nov 25, 2019 at 11:29:38AM +0100, Paolo Bonzini wrote:
> On 25/11/19 01:58, Paul Mackerras wrote:
>
> Yes, of course (I have even accepted submaintainer pull request for new
> features during the first week of the merge window, so not a problem at
> all).
In that case, I have a patchset from Bharata Rao which is just now
ready to go in. It has been around for a while; Bharata posted v11
yesterday, and we would really like it to go in v5.5, but I thought we
were too late. If you're OK with taking it at this stage then I'll
send you another pull request.
Thanks,
Paul.
next prev parent reply other threads:[~2019-11-25 23:44 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 5:14 [GIT PULL] Please pull my kvm-ppc-next-5.1-1 tag Paul Mackerras
2019-02-22 5:23 ` Masahiro Yamada
2019-02-22 5:52 ` Paul Mackerras
2019-02-22 6:46 ` Masahiro Yamada
2019-02-22 9:46 ` Paul Mackerras
2019-02-22 16:43 ` Paolo Bonzini
2019-03-01 3:37 ` [GIT PULL] Please pull my kvm-ppc-next-5.1-2 tag Paul Mackerras
2019-03-01 5:21 ` [GIT PULL] Please pull my kvm-ppc-next-5.1-3 tag Paul Mackerras
2019-03-14 3:31 ` Paul Mackerras
2019-03-15 18:13 ` Paolo Bonzini
2019-05-02 4:06 ` [GIT PULL] Please pull my kvm-ppc-next-5.2-1 tag Paul Mackerras
2019-05-02 4:06 ` Paul Mackerras
2019-05-09 22:46 ` Paul Mackerras
2019-05-09 22:46 ` Paul Mackerras
2019-05-14 10:13 ` [GIT PULL] Please pull my kvm-ppc-next-5.2-2 tag Paul Mackerras
2019-05-14 10:13 ` Paul Mackerras
2019-05-15 21:40 ` Paolo Bonzini
2019-05-15 21:40 ` Paolo Bonzini
2019-08-28 23:23 ` [GIT PULL] Please pull my kvm-ppc-next-5.4-1 tag Paul Mackerras
2019-08-28 23:23 ` Paul Mackerras
2019-09-06 12:04 ` Paul Mackerras
2019-09-06 12:04 ` Paul Mackerras
2019-09-10 14:51 ` Paolo Bonzini
2019-09-10 14:51 ` Paolo Bonzini
2019-10-31 11:13 ` [GIT PULL] Please pull my kvm-ppc-next-5.5-1 tag Paul Mackerras
2019-10-31 11:13 ` Paul Mackerras
2019-10-31 23:36 ` Paolo Bonzini
2019-10-31 23:36 ` Paolo Bonzini
2019-11-25 0:58 ` [GIT PULL] Please pull my kvm-ppc-next-5.5-2 tag Paul Mackerras
2019-11-25 0:58 ` Paul Mackerras
2019-11-25 10:29 ` Paolo Bonzini
2019-11-25 10:29 ` Paolo Bonzini
2019-11-25 23:44 ` Paul Mackerras [this message]
2019-11-25 23:44 ` Paul Mackerras
2019-11-26 8:52 ` Paolo Bonzini
2019-11-26 8:52 ` Paolo Bonzini
2020-01-21 3:33 ` [GIT PULL] Please pull my kvm-ppc-next-5.6-1 tag Paul Mackerras
2020-01-21 3:33 ` Paul Mackerras
2020-01-21 16:15 ` Paolo Bonzini
2020-01-21 16:15 ` Paolo Bonzini
2020-01-30 0:54 ` [GIT PULL] Please pull my kvm-ppc-next-5.6-2 tag Paul Mackerras
2020-01-30 0:54 ` Paul Mackerras
2020-03-30 23:08 ` [GIT PULL] Please pull my kvm-ppc-next-5.7-1 tag Paul Mackerras
2020-03-30 23:08 ` Paul Mackerras
2020-03-31 14:47 ` Paolo Bonzini
2020-03-31 14:47 ` Paolo Bonzini
2020-06-01 23:53 ` [GIT PULL] Please pull my kvm-ppc-next-5.8-1 tag Paul Mackerras
2020-06-01 23:53 ` Paul Mackerras
2020-06-04 18:58 ` Paolo Bonzini
2020-06-04 18:58 ` Paolo Bonzini
2020-06-11 0:48 ` Paul Mackerras
2020-06-11 0:48 ` Paul Mackerras
2020-06-11 1:01 ` Paolo Bonzini
2020-06-11 1:01 ` Paolo Bonzini
2020-07-28 5:51 ` [GIT PULL] Please pull my kvm-ppc-next-5.9-1 tag Paul Mackerras
2020-07-28 5:51 ` Paul Mackerras
2020-08-05 0:02 ` Paul Mackerras
2020-08-05 0:02 ` Paul Mackerras
2020-08-07 12:23 ` Paolo Bonzini
2020-08-07 12:23 ` Paolo Bonzini
2020-09-22 4:19 ` [GIT PULL] Please pull my kvm-ppc-next-5.10-1 tag Paul Mackerras
2020-09-22 4:19 ` Paul Mackerras
2020-09-22 12:18 ` Paolo Bonzini
2020-09-22 12:18 ` Paolo Bonzini
2021-02-11 7:25 ` [GIT PULL] Please pull my kvm-ppc-next-5.12-1 tag Paul Mackerras
2021-02-11 7:25 ` Paul Mackerras
2021-02-11 13:00 ` Paolo Bonzini
2021-02-11 13:00 ` 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=20191125234451.GA11896@blackberry \
--to=paulus@ozlabs.org \
--cc=bharata@linux.ibm.com \
--cc=groug@kaod.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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.