linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Wei Liu <wei.liu@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	KVM list <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] First batch of KVM changes for Linux 5.8
Date: Thu, 4 Jun 2020 18:33:33 +0200	[thread overview]
Message-ID: <8ffbd4d8-5baf-c2ee-8728-cc73794ed863@redhat.com> (raw)
In-Reply-To: <CAHk-=wjC21siUGvy9zpVOHfLRe4rwiT-ntqqj3zN73qtveKjpQ@mail.gmail.com>

On 04/06/20 00:17, Linus Torvalds wrote:
> On Wed, Jun 3, 2020 at 10:39 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>> There could be minor conflicts depending on the order you're processing 5.8
>> pull requests.
> It would have been good if you had actually pointed to the reports
> from linux-next.
> 
> As it was, the hyper-v pull request did do that (thanks Wei Liu), so I
> could verify my merge against what had been reported and this didn't
> take me by surprise, but it would have good to see that kind of detail
> from the kvm pull too..

Ok, I'll keep it in mind.  Based on today's report from Stephen, you
will get also a conflict with the s390 tree, and a semantic change
(build failure) when Thomas sends his large IRQ rework, due to the
removal of the second argument to do_machine_check.

Paolo


  reply	other threads:[~2020-06-04 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 17:38 [GIT PULL] First batch of KVM changes for Linux 5.8 Paolo Bonzini
2020-06-03 22:17 ` Linus Torvalds
2020-06-04 16:33   ` Paolo Bonzini [this message]
2020-06-03 22:30 ` pr-tracker-bot

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=8ffbd4d8-5baf-c2ee-8728-cc73794ed863@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wei.liu@kernel.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;
as well as URLs for NNTP newsgroup(s).