public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos_odonell at mentor dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug ports/14595] memset is broken on powerpc 405 Date: Wed, 19 Sep 2012 20:20:00 -0000 [thread overview] Message-ID: <bug-14595-131-Eet3lGXJ4M@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14595-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14595 Carlos O'Donell <carlos_odonell at mentor dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING CC| |carlos_odonell at mentor | |dot com --- Comment #1 from Carlos O'Donell <carlos_odonell at mentor dot com> 2012-09-19 20:20:19 UTC --- Jason, Thanks for filling an issue in the bugzilla. The patch looks like a great start, could you follow the contribution checklist and post this to libc-alpha@sourceware.org for review? http://sourceware.org/glibc/wiki/Contribution%20checklist Thanks! -- 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-09-19 20:20 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-19 20:03 [Bug ports/14595] New: " jgunthorpe at gmail dot com 2012-09-19 20:20 ` carlos_odonell at mentor dot com [this message] 2012-09-25 16:23 ` [Bug ports/14595] " rsa at us dot ibm.com 2012-09-25 16:25 ` rsa at us dot ibm.com 2012-11-29 15:47 ` [Bug ports/14595] power: " carlos_odonell at mentor dot com 2012-11-29 15:51 ` rsa at us dot ibm.com 2014-06-13 13:57 ` fweimer at redhat dot com 2014-06-13 14:00 ` fweimer at redhat dot com 2014-06-13 15:36 ` jgunthorpe at gmail dot com 2014-06-13 15:44 ` fweimer at redhat dot com 2014-06-13 15:44 ` 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-14595-131-Eet3lGXJ4M@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).