Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-next@vger.kernel.org,
	David Gibson <david@gibson.dropbear.id.au>,
	Paul Mackerras <paulus@samba.org>,
	Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Subject: linux-next: manual merge of the s390 tree
Date: Thu, 20 Nov 2008 10:13:09 +1100	[thread overview]
Message-ID: <20081120101309.0553d091.sfr@canb.auug.org.au> (raw)

Hi Martin,

Today's linux-next merge of the s390 tree got a conflict in
drivers/char/Kconfig drivers/char/Makefile between commit
d5e54913433fff89609adfc4b96fefcf807a9030 ("powerpc: udbg-based backend
for hvc_console") from the powerpc tree and commit
c7f224c72b6973056497af6bb69efce6d5a19e86 ("[S390] s390/hvc_console: z/VM
IUCV hypervisor console support") from the s390 tree.

Just overlapping additions. I fixed it up (see below) and can carry the
fix.  The conflict could be eliminated by one of the two sets of changes
moving slightly in the files (I am hinting about the s390 ones here as
Paul does not like rebasing his tree ...).
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc drivers/char/Kconfig
index f57907a,755adf7..0000000
--- a/drivers/char/Kconfig
+++ b/drivers/char/Kconfig
@@@ -631,12 -631,16 +631,22 @@@ config HVC_XE
  	help
  	  Xen virtual console device driver
  
 +config HVC_UDBG
 +       bool "udbg based fake hypervisor console"
 +       depends on PPC && EXPERIMENTAL
 +       select HVC_DRIVER
 +       default n
 +
+ config HVC_IUCV
+ 	bool "z/VM IUCV Hypervisor console support (VM only)"
+ 	depends on S390
+ 	select HVC_DRIVER
+ 	select IUCV
+ 	default y
+ 	help
+ 	  This driver provides a Hypervisor console (HVC) back-end to access
+ 	  a Linux (console) terminal via a z/VM IUCV communication path.
+ 
  config VIRTIO_CONSOLE
  	tristate "Virtio console"
  	depends on VIRTIO
diff --cc drivers/char/Makefile
index 52e1552,36151ba..0000000
--- a/drivers/char/Makefile
+++ b/drivers/char/Makefile
@@@ -50,7 -50,7 +50,8 @@@ obj-$(CONFIG_HVC_BEAT)		+= hvc_beat.
  obj-$(CONFIG_HVC_DRIVER)	+= hvc_console.o
  obj-$(CONFIG_HVC_IRQ)		+= hvc_irq.o
  obj-$(CONFIG_HVC_XEN)		+= hvc_xen.o
 +obj-$(CONFIG_HVC_UDBG)		+= hvc_udbg.o
+ obj-$(CONFIG_HVC_IUCV)		+= hvc_iucv.o
  obj-$(CONFIG_VIRTIO_CONSOLE)	+= virtio_console.o
  obj-$(CONFIG_RAW_DRIVER)	+= raw.o
  obj-$(CONFIG_SGI_SNSC)		+= snsc.o snsc_event.o

             reply	other threads:[~2008-11-19 23:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 23:13 Stephen Rothwell [this message]
2008-11-20 11:10 ` linux-next: manual merge of the s390 tree Martin Schwidefsky
2008-11-20 11:57   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-12-01 22:39 Stephen Rothwell
2008-12-02  8:12 ` Martin Schwidefsky
2008-12-02 22:09   ` Stephen Rothwell
2008-10-29  0:06 Stephen Rothwell
2008-07-01  4:43 Stephen Rothwell
2008-06-24  3:45 Stephen Rothwell
2008-06-24  4:27 ` Greg KH

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=20081120101309.0553d091.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=schwidefsky@de.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