From: Hans-Werner Hilse <hwhilse@gmail.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [PATCH] missed musl compatibility patch
Date: Fri, 26 Jun 2015 10:36:13 +0200 [thread overview]
Message-ID: <1435307774-3897-1-git-send-email-hwhilse@gmail.com> (raw)
I'm sorry but one patch that is necessary for compilation against
musl libc was still missing in the series I sent earlier.
(Thank you very much for applying!)
This is a bit awkward: It looked so nice and clean to just call
"modify_ldt()" before. The external declaration is a hint that not
all was well. Looking at modify_ldt(2), making the syscall via
syscall() ourselves is actually the recommended way, so I hope
it isn't too troublesome a patch.
Hans-Werner Hilse (1):
um: Do not rely on libc to provide modify_ldt()
arch/x86/um/ldt.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--
2.4.3
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2015-06-26 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 8:36 Hans-Werner Hilse [this message]
2015-06-26 8:36 ` [uml-devel] [PATCH] um: Do not rely on libc to provide modify_ldt() Hans-Werner Hilse
2015-06-27 18:18 ` [uml-devel] [PATCH] missed musl compatibility patch Richard Weinberger
2015-06-29 7:15 ` Hans-Werner Hilse
2015-06-29 9:50 ` [uml-devel] [PATCH v2] " Hans-Werner Hilse
2015-06-29 9:50 ` [uml-devel] [PATCH v2] um: Do not rely on libc to provide modify_ldt() Hans-Werner Hilse
2015-07-27 11:30 ` Hans-Werner Hilse
2015-07-28 21:41 ` Richard Weinberger
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=1435307774-3897-1-git-send-email-hwhilse@gmail.com \
--to=hwhilse@gmail.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