From: Jeff Dike <jdike@addtoit.com>
To: Ollie Wild <aaw@google.com>
Cc: akpm@osdl.org, 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 23:49:20 -0400 [thread overview]
Message-ID: <20060930034920.GA10307@ccure.user-mode-linux.org> (raw)
In-Reply-To: <65dd6fd50609291518s129786fbt1739c80533d1a36@mail.google.com>
On Fri, Sep 29, 2006 at 03:18:52PM -0700, Ollie Wild wrote:
> This patch as provided breaks my build due to a missing semicolon.
>
> Patch attached.
Thanks - I fixed that, but forgot to refresh the patch.
Jeff
prev parent reply other threads:[~2006-09-30 3:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 18:14 [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 ` [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 [this message]
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=20060930034920.GA10307@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