From: Jeff Dike <jdike@addtoit.com>
To: Andrew Morton <akpm@osdl.org>
Cc: dhollis@davehollis.com, Jason Lunz <lunz@falooley.org>,
Ollie Wild <aaw@google.com>,
user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH 2/2] UML - Don't roll my own random MAC generator
Date: Fri, 29 Sep 2006 23:52:34 -0400 [thread overview]
Message-ID: <20060930035234.GB10307@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20060929153853.9bab3ca7.akpm@osdl.org>
On Fri, Sep 29, 2006 at 03:38:53PM -0700, Andrew Morton wrote:
> ahem. That must have had a lot of testing ;)
It did have some - just missed a patch refresh.
> Jeff, could we pleeeeeze arrange for UML's `make allmodconfig' to work, and
> to continue to work?
It works for me - I haven't built -mm2 on x86_64 yet, but I'll check that.
Jeff
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-09-30 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 18:14 [uml-devel] [PATCH 2/2] UML - Don't roll my own random MAC generator Jeff Dike
2006-09-29 22:18 ` Ollie Wild
2006-09-29 22:38 ` Andrew Morton
2006-09-29 22:48 ` Ollie Wild
2006-09-29 23:16 ` Andrew Morton
2006-09-30 4:15 ` Jeff Dike
2006-09-30 3:52 ` Jeff Dike [this message]
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=20060930035234.GB10307@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=aaw@google.com \
--cc=akpm@osdl.org \
--cc=dhollis@davehollis.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