From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [GIT PULL 0/5] KVM: s390: Fixups for changes in merge window for 4.0
Date: Wed, 04 Mar 2015 12:42:59 +0100 [thread overview]
Message-ID: <54F6EFC3.4050909@de.ibm.com> (raw)
In-Reply-To: <1425469314-48913-1-git-send-email-borntraeger@de.ibm.com>
Am 04.03.2015 um 12:41 schrieb Christian Borntraeger:
> Paolo, Marcelo,
>
> here is a pull request for kvm/master targetting 4.0. It is based on
> 4.0-rc1 as I want all patches in an upcoming pull request against
> kvm/next as well to avoid nasty merge conflicts with other changes
> that we have pending. So my next pull request for kvm/next will
> be based on fb5bf93f84c277546473, which is the HEAD of this pull
> request.
Or just against 4.0-rc1 thus having 5 identical commits.
next prev parent reply other threads:[~2015-03-04 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 11:41 [GIT PULL 0/5] KVM: s390: Fixups for changes in merge window for 4.0 Christian Borntraeger
2015-03-04 11:41 ` [GIT PULL 1/5] KVM: s390/cpacf: Enable key wrapping by default Christian Borntraeger
2015-03-04 11:41 ` [GIT PULL 2/5] KVM: s390/cpacf: Fix kernel bug under z/VM Christian Borntraeger
2015-03-04 11:41 ` [GIT PULL 3/5] KVM: s390: fix in memory copy of facility lists Christian Borntraeger
2015-03-04 11:41 ` [GIT PULL 4/5] KVM: s390: include guest facilities in kvm facility test Christian Borntraeger
2015-03-04 11:41 ` [GIT PULL 5/5] KVM: s390: non-LPAR case obsolete during facilities mask init Christian Borntraeger
2015-03-04 11:42 ` Christian Borntraeger [this message]
2015-03-05 1:07 ` [GIT PULL 0/5] KVM: s390: Fixups for changes in merge window for 4.0 Marcelo Tosatti
2015-03-05 8:41 ` Christian Borntraeger
2015-03-05 8:47 ` Christian Borntraeger
2015-03-05 10:33 ` Paolo Bonzini
2015-03-05 17:43 ` Marcelo Tosatti
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=54F6EFC3.4050909@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox