public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug ports/3063] sysctl syscall used by ioperm() on arm Date: Tue, 23 Mar 2010 14:54:00 -0000 [thread overview] Message-ID: <20100323145400.7785.qmail@sourceware.org> (raw) In-Reply-To: <20060815175622.3063.aurelien@aurel32.net> ------- Additional Comments From jsm28 at gcc dot gnu dot org 2010-03-23 14:53 ------- Is this change still desired (I haven't followed the details of kernel development in this area)? If so, I can apply this patch (appropriately updated to apply to current sources); unlike that posted to libc-ports in November, this one is covered by a copyright assignment. -- http://sourceware.org/bugzilla/show_bug.cgi?id=3063 ------- 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:[~2010-03-23 14:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-08-15 17:56 [Bug ports/3063] New: " aurelien at aurel32 dot net 2010-03-23 14:54 ` jsm28 at gcc dot gnu dot org [this message] [not found] <bug-3063-131@http.sourceware.org/bugzilla/> 2012-02-15 17:55 ` [Bug ports/3063] " jsm28 at gcc dot gnu.org 2012-02-15 18:43 ` aurelien at aurel32 dot net
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=20100323145400.7785.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).