Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alexander Yarygin <yarygin@linux.vnet.ibm.com>
Subject: linux-next: manual merge of the borntraeger tree with the kvms390 tree
Date: Thu, 5 May 2016 14:23:22 +1000	[thread overview]
Message-ID: <20160505142322.1b519280@canb.auug.org.au> (raw)

Hi Christian,

Today's linux-next merge of the borntraeger tree got a conflict in:

  arch/s390/kvm/kvm-s390.c

between commit:

  be7c9d7ba9e4 ("KVM: s390: Populate mask of non-hypervisor managed facility bits")

from the kvms390 tree and commit:

  5c14ad932491 ("KVM: halt_polling: provide a way to qualify wakeups during poll")

from the borntraeger tree.

I fixed it up (see below) 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

diff --cc arch/s390/kvm/kvm-s390.c
index c597201a5ca9,009a10e00e80..000000000000
--- a/arch/s390/kvm/kvm-s390.c
+++ b/arch/s390/kvm/kvm-s390.c
@@@ -2985,17 -2972,13 +2986,22 @@@ void kvm_arch_commit_memory_region(stru
  	return;
  }
  
 +static inline unsigned long nonhyp_mask(int i)
 +{
 +	unsigned int nonhyp_fai = (sclp.hmfai << i * 2) >> 30;
 +
 +	return 0x0000ffffffffffffUL >> (nonhyp_fai << 4);
 +}
 +
+ void kvm_arch_vcpu_block_finish(struct kvm_vcpu *vcpu)
+ {
+ 	vcpu->valid_wakeup = false;
+ }
+ 
  static int __init kvm_s390_init(void)
  {
 +	int i;
 +
  	if (!sclp.has_sief2) {
  		pr_info("SIE not available\n");
  		return -ENODEV;

                 reply	other threads:[~2016-05-05  4:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160505142322.1b519280@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=yarygin@linux.vnet.ibm.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