public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28432] Aarch64 memcpy used on device-memory Date: Thu, 07 Oct 2021 12:59:05 +0000 [thread overview] Message-ID: <bug-28432-131-PX4vFYiX0b@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28432-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28432 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- Could you please send the patch to libc-alpha? If may check the contributor maillist [1]. Patch discussion are done on the maillist and usually patches attached on bug reports are not following up without a proper submission to maillist. [1] https://sourceware.org/glibc/wiki/Contribution%20checklist. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-07 12:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-07 12:39 [Bug libc/28432] New: " jon@solid-run.com 2021-10-07 12:59 ` adhemerval.zanella at linaro dot org [this message] 2021-10-13 12:36 ` [Bug libc/28432] " wdijkstr at arm dot com 2021-10-13 16:36 ` jon@solid-run.com 2021-10-13 18:28 ` nsz at gcc dot gnu.org 2021-10-14 4:15 ` jon@solid-run.com 2021-10-14 8:53 ` david at qore dot org 2021-10-25 16:46 ` nsz at gcc dot gnu.org 2021-10-26 7:01 ` jon@solid-run.com 2021-11-29 16:18 ` sam at gentoo dot org
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-28432-131-PX4vFYiX0b@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).