From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: joel@rtems.org
Cc: newlib@sourceware.org
Subject: Re: [PATCH] aarch64: Remove duplicated optimized memmove()
Date: Fri, 27 Oct 2023 20:19:14 +0200 [thread overview]
Message-ID: <388e1ae5-9b4f-4e63-bf3e-fb7cd8ae291d@embedded-brains.de> (raw)
In-Reply-To: <CAF9ehCWBpURSiFDd8tgVdsfeHKxNXZ+9GFyaVvDuPZxUctWgWw@mail.gmail.com>
On 27.10.23 19:15, Joel Sherrill wrote:
> This doesn't appear to resolve the issue.
I should not send patches late on Friday. Hopefully, the v2 version
fixes the problem.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
prev parent reply other threads:[~2023-10-27 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 16:59 Sebastian Huber
2023-10-27 17:15 ` Joel Sherrill
2023-10-27 18:19 ` Sebastian Huber [this message]
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=388e1ae5-9b4f-4e63-bf3e-fb7cd8ae291d@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=joel@rtems.org \
--cc=newlib@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: link
Be 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).