linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: s390/driver-core merge conflict
@ 2008-05-29  3:58 Stephen Rothwell
  2008-05-29 12:22 ` Martin Schwidefsky
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2008-05-29  3:58 UTC (permalink / raw)
  To: Martin Schwidefsky, Greg KH; +Cc: linux-next, Kay Sievers, Peter Oberparleiter

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

Hi Martin,

Today's linux-next merge of the s390 tree got conflicts in
drivers/s390/block/dasd.c, drivers/s390/block/dasd_eckd.c,
drivers/s390/block/dasd_fba.c, drivers/s390/char/tape_core.c,
drivers/s390/cio/device_fsm.c, drivers/s390/net/claw.c,
drivers/s390/net/ctcm_main.c and drivers/s390/net/lcs.c between commit
bd24b944eb93549b1ca5becbf27c7373504f7eed ("driver-core: prepare for
removal of 20 char limit from struct device") from the driver-core tree
and commits 17ae2c0d4d27d73fb264e204e385bf5436349f36 ("[S390] cio:
introduce fcx enabled scsw format") and
8e4dac6f0f36686984ed3f01b977259e3127433b ("[S390] cio: provide functions
for fcx enabled I/O") from the s390 tree.

I merged all the dev_name changes from driver-core into the s390 changes.
Someone might like to check it.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: s390/driver-core merge conflict
  2008-05-29  3:58 linux-next: s390/driver-core merge conflict Stephen Rothwell
@ 2008-05-29 12:22 ` Martin Schwidefsky
  2008-05-29 13:05   ` Stephen Rothwell
  0 siblings, 1 reply; 3+ messages in thread
From: Martin Schwidefsky @ 2008-05-29 12:22 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: Greg KH, linux-next, Kay Sievers, Peter Oberparleiter

On Thu, 2008-05-29 at 13:58 +1000, Stephen Rothwell wrote:
> Hi Martin,
> 
> Today's linux-next merge of the s390 tree got conflicts in
> drivers/s390/block/dasd.c, drivers/s390/block/dasd_eckd.c,
> drivers/s390/block/dasd_fba.c, drivers/s390/char/tape_core.c,
> drivers/s390/cio/device_fsm.c, drivers/s390/net/claw.c,
> drivers/s390/net/ctcm_main.c and drivers/s390/net/lcs.c between commit
> bd24b944eb93549b1ca5becbf27c7373504f7eed ("driver-core: prepare for
> removal of 20 char limit from struct device") from the driver-core tree
> and commits 17ae2c0d4d27d73fb264e204e385bf5436349f36 ("[S390] cio:
> introduce fcx enabled scsw format") and
> 8e4dac6f0f36686984ed3f01b977259e3127433b ("[S390] cio: provide functions
> for fcx enabled I/O") from the s390 tree.
> 
> I merged all the dev_name changes from driver-core into the s390 changes.
> Someone might like to check it.

It builds fine and it boots. Not too bad I would say.

-- 
blue skies,
  Martin.

"Reality continues to ruin my life." - Calvin.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: s390/driver-core merge conflict
  2008-05-29 12:22 ` Martin Schwidefsky
@ 2008-05-29 13:05   ` Stephen Rothwell
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2008-05-29 13:05 UTC (permalink / raw)
  To: schwidefsky; +Cc: Greg KH, linux-next, Kay Sievers, Peter Oberparleiter

[-- Attachment #1: Type: text/plain, Size: 295 bytes --]

Hi Martin,

On Thu, 29 May 2008 14:22:55 +0200 Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
>
> It builds fine and it boots. Not too bad I would say.

Thanks for the check.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-05-29 13:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-05-29  3:58 linux-next: s390/driver-core merge conflict Stephen Rothwell
2008-05-29 12:22 ` Martin Schwidefsky
2008-05-29 13:05   ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).