From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Christian Borntraeger" <borntraeger@de.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"KVM list" <kvm@vger.kernel.org>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Dan Williams" <dan.j.williams@intel.com>,
"Marc Zyngier" <marc.zyngier@arm.com>,
"Paul Mackerras" <paulus@ozlabs.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>
Subject: Re: [GIT PULL] KVM changes for 4.8 merge window
Date: Tue, 2 Aug 2016 17:36:47 -0400 [thread overview]
Message-ID: <20160802173647.2bc6f36f@mschwide> (raw)
In-Reply-To: <CA+55aFyFTW8mSwe3s2VfM=Y7AYqKgz31gqRCHQmH3C1byOeJdA@mail.gmail.com>
On Tue, 2 Aug 2016 16:17:39 -0400
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Tue, Aug 2, 2016 at 2:42 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > No, I don't use the merge from linux-next directly. I just re-generate
> > the merge myself, and if the pull request then includes a merge
> > resolution (either as just a verbal description, or a patch or by
> > having a separate "merged" test-branch), I will compare my merge with
> > that one.
>
> Ok, the KVM merge was indeed the most painful one this merge window so
> far. Which isn't saying all that much, since this merge window has so
> far been pretty good (knock wood).
>
> Let's see if I got everything right. I did pick up the fixup patch
> from Sudip and made it part of the merge, so that hopefully it's all
> complete and also bisectable.
>
> Please do check it out. And let's hope the KVM people have learnt
> their lesson and we won't have these messy merges in the future.
I included my try to fixup the expected merge conflict between the
KVM tree and the s390 tree at the end of the first please-merge email
for s390. Dunno if you have noticed this, the merge result looks good
to me.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2016-08-03 0:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 12:37 [GIT PULL] KVM changes for 4.8 merge window Paolo Bonzini
2016-08-02 18:02 ` Christian Borntraeger
2016-08-02 18:42 ` Linus Torvalds
2016-08-02 20:17 ` Linus Torvalds
2016-08-02 20:49 ` Christian Borntraeger
2016-08-02 21:36 ` Martin Schwidefsky [this message]
2016-08-02 21:46 ` Linus Torvalds
2016-08-02 18:55 ` Paolo Bonzini
2016-08-03 3:21 ` Michael Ellerman
2016-08-03 6:26 ` Paolo Bonzini
2016-08-03 6:46 ` Michael Ellerman
2016-08-03 11: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=20160802173647.2bc6f36f@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=torvalds@linux-foundation.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