public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/10972] KSM support missing: MADV_MERGEABLE and MADV_UNMERGEABLE not defined Date: Tue, 17 Nov 2009 13:36:00 -0000 [thread overview] Message-ID: <20091117133643.411.qmail@sourceware.org> (raw) In-Reply-To: <20091117133612.10972.aurelien@aurel32.net> ------- Additional Comments From aurelien at aurel32 dot net 2009-11-17 13:36 ------- Created an attachment (id=4390) --> (http://sourceware.org/bugzilla/attachment.cgi?id=4390&action=view) Patch for main architectures -- http://sourceware.org/bugzilla/show_bug.cgi?id=10972 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-11-17 13:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-17 13:36 [Bug libc/10972] New: " aurelien at aurel32 dot net 2009-11-17 13:36 ` aurelien at aurel32 dot net [this message] 2009-11-17 13:37 ` [Bug libc/10972] " aurelien at aurel32 dot net 2009-11-17 17:39 ` drepper at redhat dot com [not found] <bug-10972-131@http.sourceware.org/bugzilla/> 2014-07-01 5:21 ` fweimer at redhat dot com
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=20091117133643.411.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).