From: Paolo Bonzini <pbonzini@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, KVM <kvm@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Marcelo Tosatti <mtosatti@redhat•com>,
Sean Christopherson <seanjc@google•com>
Subject: Re: linux-next: manual merge of the kvm-fixes tree with Linus' tree
Date: Thu, 20 Jan 2022 11:47:13 +0100 [thread overview]
Message-ID: <a87499ee-8cd5-2f57-9c1a-58779b5f7047@redhat.com> (raw)
In-Reply-To: <20220120092527.71e3a85f@canb.auug.org.au>
On 1/19/22 23:25, Stephen Rothwell wrote:
> It may be worth while rebasing this fix on top of Linus' current tree.
Yes, the next pull request will include a merge commit to avoid the
conflict.
Paolo
next prev parent reply other threads:[~2022-01-20 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 22:25 linux-next: manual merge of the kvm-fixes tree with Linus' tree Stephen Rothwell
2022-01-20 10:47 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-01 21:05 Stephen Rothwell
2019-11-12 21:00 Stephen Rothwell
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=a87499ee-8cd5-2f57-9c1a-58779b5f7047@redhat.com \
--to=pbonzini@redhat$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mtosatti@redhat$(echo .)com \
--cc=seanjc@google$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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