From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: Breakage of compilation in .11-rc1 - "code-tidying" is broken
Date: Thu, 13 Jan 2005 21:19:40 +0100 [thread overview]
Message-ID: <200501132119.40389.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200501132205.j0DM5Oha005643@ccure.user-mode-linux.org>
On Thursday 13 January 2005 23:05, Jeff Dike wrote:
> blaisorblade@yahoo.it said:
> > In fact, including both linux/ptrace.h and sys/ptrace.h is not
> > redundant - it must also be done in the proper order, so I'm writing
> > a patch with the appropriate content.
> Wait till I update my patch list before fixing this. Bodo send me a patch,
> which I am polishing now.
> Jeff
I'm testing the compilation now - also, I'm commenting out part of the new
syscalls - the vperfctr ones give problems, I guess they are mm-only for now.
Instead the key managing ones already exist.
So, I've done a patch for both things and I'm posting it - preserve the
comment I added about those headers in your polished version which you'll
merge.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-01-13 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 19:08 [uml-devel] Breakage of compilation in .11-rc1 - "code-tidying" is broken Blaisorblade
2005-01-13 22:05 ` [uml-devel] " Jeff Dike
2005-01-13 20:19 ` Blaisorblade [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=200501132119.40389.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--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