From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@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 00/18] KVM: s390: Fixes and features for kvm/next (4.6)
Date: Fri, 12 Feb 2016 17:08:55 +0100 [thread overview]
Message-ID: <56BE0397.5030901@de.ibm.com> (raw)
In-Reply-To: <56BE01A3.4020801@redhat.com>
On 02/12/2016 05:00 PM, Paolo Bonzini wrote:
>
>
> On 12/02/2016 16:54, Christian Borntraeger wrote:
>> I need one patch for 4.4 as well (vs. 3 patches against 4.5-rc3). So bisect is broken
>> on 4.4 as well, I just had it fixed earlier.
>
> If these three patches are in Linus's tree, just send the pull request
> against that. It's okay if a submaintainer pull request brings back a
> few more commits from Linus's tree.
Not yet in Linus tree (cgroup-fixes mostly)
>
> Rebases aren't great, but no one should be basing a linux-next tree on
> kvm-s390/next so I guess that's not too evil a thing to do.
Yes, kvm-s390/next can certainly be rebased, right now I do not have a working
upstream commit >4.4.
What I could do is to use my old pull request for kvm/next that was
targetted for 4.5. That tree did survive some testing, so basically rebase
against kvm-s390-next-4.5-3 ?
Christian
next prev parent reply other threads:[~2016-02-12 16:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 13:22 [GIT PULL 00/18] KVM: s390: Fixes and features for kvm/next (4.6) Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 01/18] KVM: s390: allow sync of fp registers via vregs Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 02/18] KVM: s390: sync of fp registers via kvm_run Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 03/18] KVM: s390: PSW forwarding / rewinding / ilc rework Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 04/18] KVM: s390: migration / injection of prog irq ilc Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 05/18] KVM: s390: gaccess: introduce access modes Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 06/18] KVM: s390: gaccess: implement instruction fetching mode Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 07/18] KVM: s390: read the correct opcode on SIE faults Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 08/18] KVM: s390: clean up prog irq injection on prog irq icpts Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 09/18] KVM: s390: irq delivery should not rely on icptcode Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 10/18] KVM: s390: provide prog irq ilc on SIE faults Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 11/18] KVM: s390: instruction-fetching exceptions " Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 12/18] KVM: s390: remove old fragment of vector registers Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 13/18] KVM: s390: add documentation of KVM_S390_VM_TOD Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 14/18] KVM: s390: add documentation of KVM_S390_VM_CRYPTO Christian Borntraeger
2016-02-12 13:22 ` [GIT PULL 15/18] KVM: s390: usage hint for adapter mappings Christian Borntraeger
2016-02-12 13:23 ` [GIT PULL 16/18] KVM: s390: do not take mmap_sem on dirty log query Christian Borntraeger
2016-02-12 13:23 ` [GIT PULL 17/18] KVM: s390: do not block CPU on dirty logging Christian Borntraeger
2016-02-12 13:23 ` [GIT PULL 18/18] KVM: s390: bail out early on fatal signal in " Christian Borntraeger
2016-02-12 15:51 ` [GIT PULL 00/18] KVM: s390: Fixes and features for kvm/next (4.6) Paolo Bonzini
2016-02-12 15:54 ` Christian Borntraeger
2016-02-12 16:00 ` Paolo Bonzini
2016-02-12 16:08 ` Christian Borntraeger [this message]
2016-02-12 16:15 ` Christian Borntraeger
2016-02-12 16:18 ` Paolo Bonzini
2016-02-12 19:31 ` Christian Borntraeger
2016-02-12 22:25 ` Paolo Bonzini
2016-02-16 17: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=56BE0397.5030901@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=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;
as well as URLs for NNTP newsgroup(s).