From: Andrew Morton <akpm@osdl.org>
To: "Ollie Wild" <aaw@google.com>
Cc: "Jeff Dike" <jdike@addtoit.com>,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
dhollis@davehollis.com, "Jason Lunz" <lunz@falooley.org>
Subject: Re: [PATCH 2/2] UML - Don't roll my own random MAC generator
Date: Fri, 29 Sep 2006 15:38:53 -0700 [thread overview]
Message-ID: <20060929153853.9bab3ca7.akpm@osdl.org> (raw)
In-Reply-To: <65dd6fd50609291518s129786fbt1739c80533d1a36@mail.google.com>
On Fri, 29 Sep 2006 15:18:52 -0700
"Ollie Wild" <aaw@google.com> wrote:
> This patch as provided breaks my build due to a missing semicolon.
>
> ..
>
> - random_ether_addr(addr)
> + random_ether_addr(addr);
ahem. That must have had a lot of testing ;)
Jeff, could we pleeeeeze arrange for UML's `make allmodconfig' to work, and
to continue to work?
Right now it goes splut with
arch/um/os-Linux/sys-x86_64/registers.c: In function 'get_thread_regs':
arch/um/os-Linux/sys-x86_64/registers.c:85: error: 'JB_PC' undeclared (first use in this function)
arch/um/os-Linux/sys-x86_64/registers.c:85: error: (Each undeclared identifier is reported only once
arch/um/os-Linux/sys-x86_64/registers.c:85: error: for each function it appears in.)
arch/um/os-Linux/sys-x86_64/registers.c:86: error: 'JB_RSP' undeclared (first use in this function)
arch/um/os-Linux/sys-x86_64/registers.c:87: error: 'JB_RBP' undeclared (first use in this function)
How does one build uml-for-i386 on an x86_64 host, btw?
next prev parent reply other threads:[~2006-09-29 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 18:14 Jeff Dike
2006-09-29 22:18 ` Ollie Wild
2006-09-29 22:38 ` Andrew Morton [this message]
2006-09-29 22:48 ` Ollie Wild
2006-09-29 23:16 ` Andrew Morton
2006-09-30 4:15 ` [uml-devel] " Jeff Dike
2006-09-30 3:52 ` Jeff Dike
2006-09-30 4:08 ` Andrew Morton
2006-09-30 3:49 ` Jeff Dike
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=20060929153853.9bab3ca7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=aaw@google.com \
--cc=dhollis@davehollis.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lunz@falooley.org \
--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
Powered by JetHome