All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@kernel.org>,
	kvm@vger.kernel.org, Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Janosch Frank <frankja@linux.vnet.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: linux-next: manual merge of the kvm tree with the s390 tree
Date: Wed, 29 Jun 2016 07:47:50 +0200	[thread overview]
Message-ID: <20160629054750.GA3458@osiris> (raw)
In-Reply-To: <20160629143658.204b8d07@canb.auug.org.au>

On Wed, Jun 29, 2016 at 02:36:58PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the kvm tree got a conflict in:
> 
>   arch/s390/hypfs/hypfs_diag.c
> 
> between commit:
> 
>   e030c1125eab ("s390/hypfs: use basic block for diag inline assembly")
> 
> from the s390 tree and commit:
> 
>   e65f30e0cb29 ("s390: hypfs: Move diag implementation and data definitions")
> 
> from the kvm tree.
> 
> I fixed it up (my fixup patch now looks like 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.
> 
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 14 Jun 2016 14:47:33 +1000
> Subject: [PATCH] s390: merge fix up for __diag204 move
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  arch/s390/kernel/diag.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)

The fix looks good. Thanks!

  reply	other threads:[~2016-06-29  5:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  4:36 linux-next: manual merge of the kvm tree with the s390 tree Stephen Rothwell
2016-06-29  4:36 ` Stephen Rothwell
2016-06-29  5:47 ` Heiko Carstens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-29  6:46 Stephen Rothwell
2020-06-04  3:05 ` Stephen Rothwell
2016-07-14  4:03 Stephen Rothwell
2016-07-14  4:03 ` Stephen Rothwell
2016-07-14  6:58 ` David Hildenbrand
2016-07-14  6:58   ` David Hildenbrand
2014-10-07  4:59 Stephen Rothwell
2013-06-06  3:55 Stephen Rothwell
2013-06-06  3:55 ` Stephen Rothwell
2013-01-03  1:06 Stephen Rothwell
2013-01-03  7:31 ` Martin Schwidefsky
2013-01-03 10:56   ` Stephen Rothwell
2012-08-16  3:49 Stephen Rothwell
2011-09-21  3:55 Stephen Rothwell
2010-10-21  1:16 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=20160629054750.GA3458@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=frankja@linux.vnet.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.