From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Paolo Bonzini" <pbonzini@redhat•com>,
"Radim Krčmář" <rkrcmar@redhat•com>, KVM <kvm@vger•kernel.org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Christoph Hellwig <hch@lst•de>,
Linus Torvalds <torvalds@linux-foundation•org>
Subject: linux-next: manual merge of the kvm-fixes tree with Linus' tree
Date: Mon, 2 Mar 2020 08:05:43 +1100 [thread overview]
Message-ID: <20200302080543.51450371@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Hi all,
Today's linux-next merge of the kvm-fixes tree got a conflict in:
arch/x86/kvm/Makefile
between commit:
cfe2ce49b9da ("Revert "KVM: x86: enable -Werror"")
from Linus' tree and commit:
4f337faf1c55 ("KVM: allow disabling -Werror")
from the kvm-fixes tree.
I fixed it up (I just used the latter version) and can carry the fix as
necessary. This is now fixed as far as linux-next is concerned, but any
non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging. You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-03-01 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 21:05 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=20200302080543.51450371@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hch@lst$(echo .)de \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
--cc=rkrcmar@redhat$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/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