All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: xen pv_ops git merge conflicts unresolved?
Date: Tue, 03 Mar 2009 11:14:17 +0100	[thread overview]
Message-ID: <1236075257.6787.7.camel@marc> (raw)

Hello Jeremy,


it looks like there were some merge conflicts yesterday on the following
commits/files and they didn't got resolved properly...

commit 5b82413a71a831afe91f3b3b7242deea06d65a8c

Conflicts:
arch/x86/kernel/ioport.c
arch/x86/kernel/process_64.c
arch/x86/mm/pgtable.c
arch/x86/xen/Kconfig


commit c98c8642f3d2df5567404f348c4d370c8ccc0846

Conflicts:
arch/x86/kernel/process_32.c


A build fails now with:

  CC      arch/x86/kernel/process_32.o
arch/x86/kernel/process_32.c:461:3: warning: "/*" within comment
arch/x86/kernel/process_32.c:462: error: expected ')' before '(' token
arch/x86/kernel/process_32.c:463: error: expected identifier or '('
before '}' token
arch/x86/kernel/process_32.c:464: warning: data definition has no type
or storage class
arch/x86/kernel/process_32.c:464: warning: type defaults to 'int' in
declaration of 'putname'
arch/x86/kernel/process_32.c:464: warning: parameter names (without
types) in function declaration
arch/x86/kernel/process_32.c:464: error: conflicting types for 'putname'
include/linux/fs.h:1734: error: previous declaration of 'putname' was
here
arch/x86/kernel/process_32.c:465: error: expected '=', ',', ';', 'asm'
or '__attribute__' before ':' token
arch/x86/kernel/process_32.c:467: error: expected identifier or '('
before '}' token
make[1]: *** [arch/x86/kernel/process_32.o] Error 1
make: *** [arch/x86/kernel] Error 2


Marc

             reply	other threads:[~2009-03-03 10:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 10:14 Marc - A. Dahlhaus [ Administration | Westermann GmbH ] [this message]
2009-03-03 13:08 ` xen pv_ops git merge conflicts unresolved? Ian Campbell
2009-03-03 17:33   ` Jeremy Fitzhardinge

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=1236075257.6787.7.camel@marc \
    --to=mad@wol.de \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.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 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.