mailing list of musl libc
 help / color / mirror / code / Atom feed
From: idunham@lavabit.com
To: musl@lists.openwall.com
Subject: Re: [PATCH] vm86 syscall wrappers
Date: Thu, 16 Aug 2012 20:58:56 -0400 (EDT)	[thread overview]
Message-ID: <57347.132.241.65.36.1345165136.squirrel@lavabit.com> (raw)
In-Reply-To: <502D9503.50505@gentoo.org>

> On 08/17/2012 02:32 AM, idunham@lavabit.com wrote:
>> +	unsigned long is_vm86pus:1;
>
> typo?

Nope, that's what asm/vm86.h calls it.
(note: rather than #include files from the kernel headers, I followed the
standing practice for musl and copied the relevant definitions, without
any comments. This means you don't need to install kernel headers for the
target before you can cross-compile)





      reply	other threads:[~2012-08-17  0:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17  0:32 idunham
2012-08-17  0:49 ` Luca Barbato
2012-08-17  0:58   ` idunham [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=57347.132.241.65.36.1345165136.squirrel@lavabit.com \
    --to=idunham@lavabit.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).