public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14809] glibc's sysctl.h uses incorrect <linux/kernel.h> header guard macro starting with kernel-3.7.x Date: Wed, 28 Nov 2012 15:43:00 -0000 [thread overview] Message-ID: <bug-14809-131-lSBVacL0AS@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14809-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14809 Andreas Schwab <schwab@linux-m68k.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID --- Comment #7 from Andreas Schwab <schwab@linux-m68k.org> 2012-11-28 15:43:40 UTC --- The patch has been reverted since it was a kernel bug. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-11-28 15:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-05 20:30 [Bug libc/14809] New: glibc's sysctl.h thinks it knows the <linux/kernel.h> feature test macro kkeithle at redhat dot com 2012-11-05 20:33 ` [Bug libc/14809] " kkeithle at redhat dot com 2012-11-05 20:36 ` [Bug libc/14809] glibc's sysctl.h uses incorrect <linux/kernel.h> feature test macro starting with kernel-3.7.x kkeithle at redhat dot com 2012-11-06 14:25 ` kkeithle at redhat dot com 2012-11-06 14:33 ` [Bug libc/14809] glibc's sysctl.h uses incorrect <linux/kernel.h> header guard " kkeithle at redhat dot com 2012-11-07 8:48 ` aj at suse dot de 2012-11-07 20:43 ` aj at suse dot de 2012-11-13 0:15 ` carlos_odonell at mentor dot com 2012-11-13 8:06 ` aj at suse dot de 2012-11-27 14:17 ` schwab@linux-m68k.org 2012-11-28 15:43 ` schwab@linux-m68k.org [this message] 2014-06-14 11:13 ` 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=bug-14809-131-lSBVacL0AS@http.sourceware.org/bugzilla/ \ --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).