From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>,
Richard Weinberger <richard@nod.at>
Subject: Re: linux-next: Tree for Jan 19 (uml)
Date: Wed, 18 Jan 2012 19:07:24 -0800 [thread overview]
Message-ID: <4F1788EC.4040901@xenotime.net> (raw)
In-Reply-To: <20120119125932.a4c67005cf6a0938558e8b36@canb.auug.org.au>
On 01/18/2012 05:59 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120118:
>
> Linus' tree gained a build failure for which I applied a patch.
Building uml on x86_64 gives:
CC arch/um/kernel/asm-offsets.s
In file included from /next/linux-next-20120119/arch/um/include/shared/registers.h:9:0,
from /next/linux-next-20120119/arch/um/include/asm/processor-generic.h:14,
from /next/linux-next-20120119/arch/x86/um/asm/processor.h:20,
from /next/linux-next-20120119/arch/um/include/asm/uaccess.h:16,
from /next/linux-next-20120119/arch/um/include/asm/thread_info.h:13,
from /next/linux-next-20120119/include/linux/thread_info.h:53,
from /next/linux-next-20120119/include/linux/preempt.h:9,
from /next/linux-next-20120119/include/linux/spinlock.h:50,
from /next/linux-next-20120119/include/linux/seqlock.h:29,
from /next/linux-next-20120119/include/linux/time.h:8,
from /next/linux-next-20120119/include/linux/timex.h:56,
from /next/linux-next-20120119/include/linux/sched.h:57,
from /next/linux-next-20120119/arch/x86/um/shared/sysdep/kernel-offsets.h:2,
from /next/linux-next-20120119/arch/um/kernel/asm-offsets.c:1:
/next/linux-next-20120119/arch/x86/um/shared/sysdep/ptrace.h:7:20: error: redefinition of 'regs_return_value'
/next/linux-next-20120119/arch/x86/um/shared/sysdep/ptrace.h:7:20: note: previous definition of 'regs_return_value' was here
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2012-01-19 2:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 1:59 linux-next: Tree for Jan 19 Stephen Rothwell
2012-01-19 3:07 ` Randy Dunlap [this message]
2012-01-19 2:18 ` linux-next: Tree for Jan 19 (uml) Stephen Rothwell
2012-01-19 3:40 ` Linus Torvalds
2012-01-19 22:27 ` linux-next: Tree for Jan 19 (block/nvme) Randy Dunlap
2012-01-19 22:35 ` linux-next: Tree for Jan 19 (mm/memcontrol.c) Randy Dunlap
2012-01-20 0:00 ` KAMEZAWA Hiroyuki
2012-01-20 11:09 ` Glauber Costa
2012-01-19 23:43 ` linux-next: Tree for Jan 19 (cisco/enic) Randy Dunlap
2012-01-20 5:33 ` Roopa Prabhu
2012-01-20 5:45 ` Roopa Prabhu
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=4F1788EC.4040901@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).